Claude API MCP connector
Your own product calls the model, the model calls the gateway, and your customer keys stay yours.
When you build on the Messages API you can hand the model a remote MCP server. Point it at the gateway and the model gets tools whose credentials it never sees, with your approval policy in front of every write.
Connect it
{
"model": "claude-…",
"messages": [ … ],
"mcp_servers": [
{
"type": "url",
"url": "https://mcp.sallyport.cloud/mcp",
"name": "sallyport",
"authorization_token": "sp_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}
]
}Give each of your customers their own workspace and their own agent identity. The token in the body then scopes the model to that customer alone, and their journal is theirs to export.
Field names for the connector come from the vendor and change with their beta headers. `sp init --client claude-api` prints the current body for the version you are on.