Connect your AI agent
Connecting OtoCo to an AI agent lets that agent use OtoCo tools on your behalf — discover products, start formation checkout, and (with your API key) manage entities you own.
What's an MCP?
Model Context Protocol (MCP) is an open standard that lets AI agents connect to external apps and services. OtoCo’s MCP server uses Streamable HTTP at /mcp and shares one capability registry with REST /v1.
Access tiers
| Access | Header | What your agent can do |
|---|---|---|
| Public | None | Discovery, name checks, Instant/Standalone email checkout |
| API key | Authorization: Bearer otoco_sk_… | Public tools + your entities, documents, payments, banking (per scopes) |
Create an API key first
If you need private tools (your entities, payments, banking), get a key before connecting:
- Open DashPanel → Developer.
- Sign in (connect your wallet if prompted).
- Create an API key and copy the full
otoco_sk_…token once. - Keep it ready to paste into your MCP client as
Authorization: Bearer otoco_sk_….
Full walkthrough: How to get an API key.
Staging (currently live for MCP): https://api-staging.otoco.io/mcp · Production target: https://api.otoco.io/mcp
The connect panel below uses the same env-aware base URL as the API playground (NEXT_PUBLIC_MCP_API_URL / NEXT_PUBLIC_API_URL, defaulting to staging while production /mcp rolls out).
Connect your AI agent
Connect your AI agent
Choose a platform, then follow the steps. Public discovery tools work without a key. For your entities and payments, replace otoco_sk_YOUR_API_KEY with a key from DashPanel → Developer.
MCP URL: https://api-staging.otoco.io/mcp
- Click Add to Cursor for a public-tools install (URL only — no placeholder key).
- To unlock your entities and payments, paste the API-key config into Cursor Settings → Tools & MCPs and replace
otoco_sk_YOUR_API_KEYwith a real key. Do not use a deeplink with a placeholder Bearer — Cursor sends it literally and gets401. - Reconnect the OtoCo MCP server and verify tools appear.
{
"url": "https://api-staging.otoco.io/mcp"
}{
"url": "https://api-staging.otoco.io/mcp",
"headers": {
"Authorization": "Bearer otoco_sk_YOUR_API_KEY"
}
}Never commit API keys to git or paste them into public chats. Revoke a key immediately if it leaks.
Troubleshooting
- Confirm your client supports Streamable HTTP MCP and is posting to
/mcp(GET/DELETE return405). - If private tools are missing, check that the Authorization header is present and the key is not revoked.
- Invalid or expired Authorization on MCP returns unauthorized — it does not silently fall back to public tools.
- For charge/confirm issues, make sure the agent runs a preview first, then confirms only after your explicit yes.
- Disconnect and reconnect the OtoCo MCP server after changing keys or URLs.