Build on Semuko.
One versioned catalog powers both a REST API at /api/v1 and an MCP server at /api/v1/mcp. Use it from scripts, Make, n8n, or your AI app of choice.
API & MCP on Studio Pro and Agency Unlimited
From zero to 200 OK in three steps.
Open Settings → Preferences → Developer in Semuko Admin. Copy the secret; it is shown once and stored as a SHA-256 hash.
Send it as a Bearer token. Staff login sessions are never accepted on /api/v1.
Point Claude, ChatGPT, Gemini CLI or Cursor at the MCP URL. Same key, filtered tools.
129 operations. Poke at any of them.
Each operation is both a REST route and an MCP tool, with the same scopes. Layers go from reading CRM data (L1), to money and paperwork (L2), to actions that reach clients (L3).
Least privilege, by default.
New keys start with crm.read only. Toggle scopes to see what a key can reach. Write scopes include their read scope automatically.
Plug your studio into any AI client.
The MCP server uses Streamable HTTP. Tools are filtered by the key's scopes, and hard deletes are never exposed.
oat_ prefix and are hashed at rest. Discovery: /.well-known/oauth-authorization-serverDon't poll. Get pinged.
Subscribe with POST /api/v1/webhooks. Each delivery is a JSON POST with an event, timestamp and data envelope.
Predictable when things go sideways.
When you connect MCP to a third-party AI, any CRM data you request is sent to that model. Only grant the scopes you need.
Ship something weird and useful.
Prefer no-code? Zapier keeps working on /api/zapier. See all integrations.