Synapse MCP

Live

OAUTH 2.0

DEVELOPER TOOLS

Developer Tools

Connect to Synapse MCP. Build, deploy, and manage financial data pipelines with Synapse's banking-as-a-service infrastructure from your AI workflows.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Synapse MCP
agent · Acme Q3
Run
Get Entity in Synapse MCP
S
synapsemcp_get_entity
85ms
Synapse MCP agent
Return synapse entity metadata by id (projects, folders, files, tables, etc.). only retrieves metadata information - doe.
Sources: Synapse MCP
synapsemcpmcp
1 tool call
18:29
Message Claude...

Synapse MCP tools for AI agents

CALL ANY TOOL
8 tools covering create, get, list.
synapsemcp_get_entity
Return synapse entity metadata by id (projects, folders, fil
Return synapse entity metadata by id (projects, folders, files, tables, etc.). only retrieves metadata information - does not download file content.
Parameters
Name
Type
Required
Description
entity_id
string
Required
The Synapse entity ID to fetch (for example syn123456).
synapsemcp_get_entity_annotations
Return custom annotation key/value pairs for a synapse entit
synapsemcp_get_entity_children
List children for synapse container entities (projects or fo
synapsemcp_get_entity_provenance
Return provenance (activity) metadata for a synapse entity,
synapsemcp_search_synapse
Search synapse entities using keyword queries with optional
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="synapsemcp")

mcp = MultiServerMCPClient({
"synapsemcp": {
"url": "https://mcp.scalekit.com/synapsemcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "synapsemcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/synapsemcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "synapsemcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/synapsemcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="synapsemcp")
# Connect to MCP at https://mcp.scalekit.com/synapsemcp
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Search Synapse entities using keyword queries with optional name/type/parent filters?
Copy the prompt
Copied
Return provenance (activity) metadata for a Synapse entity, including inputs and code executed?
Advanced
Copy the prompt
Copied
Search Synapse entities using keyword queries with optional name/type/parent filters?
Copy the prompt
Copied
Return provenance (activity) metadata for a Synapse entity, including inputs and code executed?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Synapse MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Synapse MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Synapse MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Synapse MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
DevOps assistant agent
Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs by feature, fix, or chore and publish release notes per tag. No manual changelog grooming.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Synapse as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Synapse OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Synapse?
Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Synapse.

What happens when a user revokes Synapse access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does entity access follow Synapse project permissions?
Yes. Entity reads, annotations, and provenance queries run as the authorizing user, so Sage Bionetworks project ACLs and governance restrictions apply to every call.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""synapsemcp"": {
""url"": ""https://mcp.scalekit.com/synapsemcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.synapsemcp]
url = ""https://mcp.scalekit.com/synapsemcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""synapsemcp"": {
""url"": ""https://mcp.scalekit.com/synapsemcp"",
""type"": ""http""
}
}
}