BYOK + local-only
Credentials and runtime operation stay under local user control.
v0.8.0 Early Access
Local-first MCP gateway for AI providers and REST APIs.
Local-first MCP gateway for AI providers and REST APIs - with explicit cost, latency, and request-level visibility.
Why this matters
One control surface without provider-specific coupling
Developers need a single control surface without hardwiring the UI to provider SDKs.
Hidden retry, backoff, and silent fallback create non-deterministic behavior and trust gaps.
Product model
Thin-shell UI. Single core boundary.
The production UI path follows a single core boundary: configure, dispatch, and render.
The core remains provider-agnostic by design.
Value pillars
Core operating principles
Deterministic execution
Explicit outcomes by design: no hidden retry, backoff, or silent fallback.
Request-level traceability
A local audit trail remains available for every request path.
How it works
Configure. Dispatch. Render.
The UI remains a thin shell: it configures intent, dispatches through a single core boundary, and renders explicit outcomes.
-
Configure in the UI
Define request intent and the connection context.
-
Dispatch through the core boundary
The core handles execution, provider protocols, and policy logic.
-
Render explicit outcomes
The UI renders results or explicit errors with no hidden retry, backoff, or silent fallback.
Trust and boundaries
Release integrity and explicit operating boundaries.
Current public lane: v0.8.0 Early Access.
Public releases include a version tag, SHA256 checksums, and release notes.
While unsigned Windows distribution remains active, unsigned status is explicitly disclosed.
Security disclosures: security@solidsynapse.com
- BYOK/local-only operation
- Not a hosted SaaS proxy
- Not a shared-key service
- Non-streaming on the product path in this lane unless explicitly approved
- No hidden retry, backoff, or silent fallback
Product surfaces
Operational surfaces, not black boxes.
Connections, REST sources, usage, and policy controls remain visible through the same local control plane.
- Dashboard
- Connections
- REST Sources
- History
- Budget Guards
- Persona Lite
FAQ
Common questions
Is mcp synapse a hosted proxy service?
No. mcp synapse is BYOK/local-only and is not positioned as a hosted or shared proxy service.
Does the product path support streaming?
No. Streaming is not supported on the product path in this lane unless it is explicitly approved.
Can I switch providers without rewriting the UI surface?
Yes. mcp synapse is designed to keep the UI path provider-agnostic through a single core boundary.
Can I connect non-LLM REST APIs?
Yes. v0.8.0 includes a REST adapter. Any JSON endpoint can be exposed as an MCP tool through the same local gateway.
Which providers are supported?
OpenAI, Azure OpenAI, Vertex AI, Anthropic, Groq, Gemini, OpenRouter, DeepSeek, xAI, Hugging Face, Ollama, and Amazon Bedrock (Early Access).
Does Budget Guard only monitor, or can it enforce?
Both. Budget Guards support monitor, block, and throttle modes.
How does cost visibility work?
mcp synapse normalizes cost across providers and shows whether each value is known, estimated, or unknown - no false certainty.
What is the current public release stage?
The current public lane is v0.8.0 Early Access.
Do you store my keys?
No. Credentials remain under local user control in the current BYOK/local-only operating model.
Download the Windows release
mcp synapse is available in the current v0.8.0 Early Access lane.