Connect each upstream
Add MCP servers with OAuth or a bearer token. Two accounts from the same provider can live side by side.
Connect multiple MCP accounts, even the same provider twice. Then choose which tools Claude can use, which calls need approval, and what responses must be guarded.
No card required · $6.50 USD per workspace/month after trial
/mcp/writing12 of 47 toolsnotion-searchSearch pages and databasesnotion-create-pageCreate a pagegithub-create-issueCreate an issueKeep work and personal accounts distinct, expose only what a task needs, then add one stable URL to Claude.
Add MCP servers with OAuth or a bearer token. Two accounts from the same provider can live side by side.
Publish only the tools Claude needs, then add ask-first rules, redaction, size limits, and injection flags.
Paste the workspace connector URL once. The Engine handles routing, credential refresh, and the audit trail.
workspace.synaxis.cloud/mcp/writingCurated connectors turn a raw tool catalog into a deliberate surface. Rules live beside the endpoint they govern.
Expose a focused subset instead of every tool definition.
Park ask-first calls until an operator approves or denies them.
Redact secrets, cap results, and flag instruction-shaped content.
Record the call path and replay safe requests through current policy.
notion-create-pagewriteNotion · Work wants to create a page in Launch notes.
{
"title": "Q3 release",
"parent": "Launch notes"
}The platform handles identity, billing, and fleet operations. Tool calls go to the isolated workspace Engine, where credentials and policy stay.
/mcp/writingUpstream tokens never reach the browser or private Platform.
A connector token is valid only for its exact endpoint and epoch.
Aggregation, approvals, guardrails, audit, recording, and replay.
Try one managed workspace for seven days with no card. When the trial ends, subscribe through Paystack to keep access active.
Trial allowance: 2,000 tool calls, 2 active hours, and 0.5 GiB transfer.
No card required for the trial.
Run the Apache 2.0 Engine yourself when you want complete infrastructure control. Its MCP runtime and policy layer do not depend on a Synaxis account.
View the Engine on GitHub$ git clone https://github.com/olumideokubadejo/synaxis-engine $ cd synaxis-engine $ docker build -t synaxis-engine . $ docker run -p 8080:8080 synaxis-engine ✓ ready http://localhost:8080/mcp