OneDroid Synapse

npx add-mcp 'https://synapse.onedroid.ai/agent/mcp'

OneDroid Synapse — Governed MCP Gateway for AI Agents

OneDroid Synapse is a governed MCP gateway. Your agents connect once; every tool call is authenticated, policy-checked, and logged while the hub's activity logging is on (fail-open: a logging failure never blocks a call), to an audit log you own.

Canonical: https://onedroid.ai/synapse

OneDroid

Governed MCP gateway

OneDroid Synapse

One connection point for all your AI tools.

OneDroid Argus installs Synapse. You can also run it on its own.

Connect the accounts you choose — Google Workspace, Atlassian, Slack — and your agents connect once. Every tool call is authenticated, policy-checked, and logged while the hub's activity logging is on (fail-open: a logging failure never blocks a call), to an audit log you own.

Open Synapse See how it works

Free on the hosted shape, whatever the size of your team. No credit card.

agents  →  onedroid synapse  →  tools

event log illustrative

About this app

What OneDroid Synapse does.

OneDroid Synapse is a gateway between AI agents and your accounts. You connect the services you choose — Google Workspace, Atlassian, Slack, and others — and agents you authorize can then act on them through one governed connection: sending an email you asked for, adding a calendar event, editing a document, updating a ticket. Access exists only for accounts you explicitly connect, is limited to the permissions you grant, and every action is logged while the hub's activity logging is on (fail-open: a logging failure never blocks a call), to an audit log you own. Disconnect an account at any time and OneDroid Synapse's access ends with it.

When you connect a Google account, OneDroid Synapse uses your Google user data solely to carry out the actions you or your authorized agents explicitly request — such as sending email you compose, managing your calendar, and creating or editing documents, spreadsheets, and presentations. Your data is never used for advertising and never used to train AI models, and access can be revoked at any time in OneDroid Synapse or in your Google account settings. Full details: Privacy Policy · Terms of Service.

“How do I control what people connect their agents to? What data does it send? Is it compliant?”

— every platform and security lead, eventually

Agents are being wired to production databases, SaaS accounts, and internal APIs today — one config file at a time, invisible to the people responsible for the answer. OneDroid Synapse replaces scattered, unaccountable connections with a single gateway that your team can see, scope, and prove.

How it works

Connect. Govern. Prove.

01

Connect

Agents point at one MCP URL instead of dozens of servers. Claude Code, Cursor, the Agent SDKs — anything that speaks MCP connects without custom integration.

"synapse": { "url": "https://synapse.onedroid.ai/hub/work/mcp" }

02

Govern

Admins decide which tools each hub, role, and agent can reach — as curated packs, not one-off allowlists. Users connect their own credentials once; agents never handle raw tokens.

03

Prove

Every call is logged while the hub's activity logging is on (fail-open: a logging failure never blocks a call): who, which tool, when, from which agent. When someone asks what your agents did last quarter, the answer is a query, not an investigation.

Capabilities

Governance without slowing anyone down.

One URL for every agent

MCP-native gateway in front of all your tool servers. Add or swap upstreams without touching a single agent config.

Packs

Curated toolsets with the context to use them safely — tools, skills, and knowledge shipped together, versioned, and scoped per hub.

Credential custody

People connect accounts once through OneDroid Synapse. Agents invoke tools under those grants without ever seeing the underlying tokens.

Audit log

An append-only event log of every tool invocation while the hub's activity logging is on — caller, tool, arguments hash, latency, result class. Yours to query and export.

Hubs and roles

Separate workspaces for teams and projects, each with its own tool surface, members, and defaults. Access follows the org chart, not tribal knowledge.

Context that persists

OneDroid Engram ships with OneDroid Synapse — durable, versioned context every agent can read and write, searched by meaning and keyword together. Change harness or model and the context stays where it is.

Why this matters

When a frontier model is just an

API call away, context is the moat.

Your competitors buy the same models, on the same terms, with the same API key. The model is a brain in a jar — swappable, and getting cheaper. What it knows about your business is not.

That knowledge is context: access to your data, access to your tools, and memory that persists between sessions and survives a change of model. OneDroid is where those three live, governed — so your team spends its time on the context instead of the plumbing.

The plumbing isn't the hard part. The plumbing that passes review is.

Bring your own database

Your data lives in your database.

With your own database, your Engram content lives in a Postgres you own; on the hosted gateway OneDroid still holds encrypted credentials and sees tool-call metadata; self-hosted, OneDroid sees nothing at runtime. The same model whether you're a single developer or a Fortune 500.

Data governance

Your database, your jurisdiction, your retention policy. Governance data never has to leave your infrastructure.

No lock-in

Export is a SQL query — the data was never ours to hold. Leave whenever you want and take everything with you.

Any scale

A free personal hub and a regulated enterprise deployment use the same mechanism. Nothing to re-architect as you grow.

The OneDroid suite

Synapse is the run layer. There's more around it.

OneDroid Synapse

Governed MCP gateway. One connection point, full governance.

Production

OneDroid Engram

Portable, persistent, permissioned context for every AI application — versioned, searchable by any MCP client, stored in your own database or hosted by OneDroid.

Available with OneDroid Synapse Learn more

OneDroid Argus

Automated end-to-end testing for software built by AI coding agents — withheld acceptance scenarios, a verdict, and evidence anyone can replay.

Sign up to evaluate Learn more

The kits

Skills, patterns, and verification gates for autonomous, evidence-gated software delivery. Free and open — we help enterprises adopt it.

Open source Learn more

Enterprise

Fully govern your AI agent and MCP infrastructure, on your infrastructure.

Active Learn more

Why OneDroid

AI governance, data, and tools

that belong to you.

Ownership

State, credentials, audit records, and configuration live where you deploy them. Nothing is held hostage on someone else's servers.

Portability

Works with any LLM, any MCP client, any infrastructure. Switch providers without losing your tools, policies, or history.

Honesty

We publish limitations alongside capabilities and say what doesn't work yet. If a claim can't be verified, we don't make it.

The actual product

Not a mockup.

The animation further up this page is illustrative and labelled as such. These are screenshots of OneDroid Synapse itself.

Governance, as switches. PHI detection, credential encryption, an append-only audit trail, long-term compliance logging, rate limiting, IP allowlisting. The padlocked rows are forced on by a platform-wide override and cannot be turned off for an individual hub — which is the difference between a policy and a suggestion.

Connections. Every upstream the hub can reach, each with its transport, its auth method and an independent on/off toggle. Note "My credential" on each one: enabling a connection for the hub does not hand anybody else your token.

Hub dashboard. Members, groups, connections and API tokens for a single hub. The hub is the boundary access is granted at — rather than a config file on somebody's laptop.

FAQ

Questions people actually ask.

What is OneDroid Synapse?

A governed MCP gateway. Your AI agents connect to one URL instead of holding their own credentials for each service, and every tool call is authenticated, checked against policy, and logged while the hub's activity logging is on (fail-open: a logging failure never blocks a call), to an audit log you own. Longer explanation.

Is OneDroid Synapse free?

Yes, on the hosted shape, whatever the size of your team, including the event log, which is not a paid tier. Enterprise is an annual licence and begins when you need deployment on your own infrastructure, org-wide policy enforcement, SSO, or audit evidence packs for compliance reviews. Pricing.

Does OneDroid Synapse work with Claude Code and Cursor?

Yes. OneDroid Synapse speaks MCP over HTTP, so any MCP-compatible client works, with any model provider. Connecting Claude Code takes a single claude mcp add command with a bearer token. See the quickstart.

Where does my data live with OneDroid?

You choose. Point OneDroid Engram at a Postgres you own and documents, embeddings, revision history and permissions are rows in your database. Self-host OneDroid Synapse and credentials and the event log stay inside your own boundary as well. Details.

What can OneDroid see?

It depends on the deployment topology. Hosted: tool-call metadata and encrypted credentials. Hosted with your own database: the same, minus your OneDroid Engram content. Self-hosted: nothing at runtime. Security & deployment.

Do I have to use your database?

No. Bring-your-own is supported precisely so leaving is cheap: the data was already in your Postgres, so there is nothing to export.

Put a gateway between your agents and the world.

Open Synapse Talk to us

Free on the hosted shape, whatever the size of your team. For another deployment shape, email michal@onedroid.ai — you'll reach Michal Bacia, the team that builds the product, not a sales queue. We reply within one business day.