Synaxis
Managed workspaces · Apache 2.0 Engine

One governed path from Claude to your tools.

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

Workspace model
Isolated Engine
Credentials
AES-256-GCM
Data path
Direct to Engine
Synaxis connector console showing a curated writing connector and a sensitive Notion tool waiting for approval.
workspace.synaxis.cloudEngine healthy
SynaxisMCP gateway
Accounts 4 Connectors 3 Approvals 2 Activity
Engine healthy4 accounts online
ConnectorWriting
Live
/mcp/writing12 of 47 tools
ToolAccountPolicy
notion-searchSearch pages and databases
Notion · WorkRead
notion-create-pageCreate a page
Notion · WorkAsk first
github-create-issueCreate an issue
GitHubGuarded
1,284 calls this month118 ms median latency
Approval requirednotion-create-pageNothing sent upstream yet
1 connector URL in ClaudeOAuth 2.1 both directionsAsk first on sensitive toolsApache 2.0 open Engine
From accounts to one connector

Three moves.
One governed endpoint.

Keep work and personal accounts distinct, expose only what a task needs, then add one stable URL to Claude.

01
Accounts

Connect each upstream

Add MCP servers with OAuth or a bearer token. Two accounts from the same provider can live side by side.

NO Notion · WorkNO Notion · PersonalGH GitHub
02
Policy

Shape the connector

Publish only the tools Claude needs, then add ask-first rules, redaction, size limits, and injection flags.

12 tools exposed 2 ask-first rules response guards on
03
Claude

Add one URL

Paste the workspace connector URL once. The Engine handles routing, credential refresh, and the audit trail.

workspace.synaxis.cloud/mcp/writing
Control before execution

Decide what Claude can do before it does it.

Curated connectors turn a raw tool catalog into a deliberate surface. Rules live beside the endpoint they govern.

Curated tool sets

Expose a focused subset instead of every tool definition.

Human approvals

Park ask-first calls until an operator approves or denies them.

Response guardrails

Redact secrets, cap results, and flag instruction-shaped content.

Inspectable audit

Record the call path and replay safe requests through current policy.

Writing connectorPending approval
02:42
notion-create-pagewrite

Notion · Work wants to create a page in Launch notes.

{
  "title": "Q3 release",
  "parent": "Launch notes"
}
Ask-first rule matchedNothing has reached Notion yet.
DenyApprove once
A deliberate trust boundary

Private platform.
Open data plane.

The platform handles identity, billing, and fleet operations. Tool calls go to the isolated workspace Engine, where credentials and policy stay.

Private PlatformIdentity · billing · provisioningNo upstream credentials
workspace tenant edge
Apache 2.0 EngineOAuth · policy · audit · MCP/mcp/writing
direct tool traffic
NO NotionLI LinearGH GitHub
Credentials stay in the Engine

Upstream tokens never reach the browser or private Platform.

Audience-bound access

A connector token is valid only for its exact endpoint and epoch.

The core stays open

Aggregation, approvals, guardrails, audit, recording, and replay.

Simple managed pricing

Seven days free.
Then $6.50 USD a month.

Try one managed workspace for seven days with no card. When the trial ends, subscribe through Paystack to keep access active.

  • 7-day trial with no card required
  • 10,000 tool calls and 8 active hours monthly
  • 2 GiB monthly transfer allowance
  • One isolated Engine per workspace
  • Secure monthly billing through Paystack

Trial allowance: 2,000 tool calls, 2 active hours, and 0.5 GiB transfer.

Starter workspace$6.50 USDper workspace · per monthStart the free trial

No card required for the trial.

Own the runtime

Keep the Engine
inside your boundary.

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
synaxis-engine
$ 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