Public API + MCP
Semuko has an MCP server and a REST API on the same catalog. Connect Claude, ChatGPT, Gemini CLI or Cursor to look up leads, create invoices, or send a contract, limited to the scopes on the key.
API & MCP are included on Studio Pro and Agency Unlimited. Account admins create keys in Settings → Preferences → Developer. New keys start read-only.
Operations, each available as REST and as an MCP tool
Scopes, from read-only CRM to sending
Request limit per key
Copying client details into a chat window is slow, and handing over a full login is risky.
Pasting CRM data into chat by hand
Your assistant calls Semuko tools directly: list leads, get an event, create a project.
All-or-nothing access
Each key or OAuth grant carries scopes. The MCP server only lists tools those scopes allow.
Custom builds that break on undocumented endpoints
A versioned /api/v1 with an OpenAPI 3.1 document generated from the same catalog.
One catalog. REST for your code, MCP for your assistant.
An account admin creates a key and picks scopes. The secret is shown once and stored hashed.
Add the Semuko MCP URL to Claude, Cursor or Gemini CLI with the key, or connect ChatGPT through OAuth.
OAuth clients go through a consent screen where an admin sees the requested scopes before approving.
Ask for this week’s unpaid invoices or a new lead. Sends are marked so your client asks before running them.
Start a free Studio Pro trial, create a read-only key, and connect your assistant. API & MCP are on Studio Pro and Agency Unlimited.
Guardrails come from the server, not from the prompt.
Bearer API keys for scripts and local clients. OAuth 2.1 with PKCE for remote MCP clients. Staff logins are never accepted.
A crm.read key only sees read tools. Sending email, invoices or contracts needs the comms.send scope.
Client-facing tools are marked destructive so MCP clients ask before running them. Hard deletes of CRM records are not exposed.
Every REST and MCP call is logged with the key, operation, status and request ID.
Subscribe your endpoint to events like lead created or contract signed, through the API or in Settings.
120 requests per minute per key or OAuth token. Large MCP results are trimmed at 200 KB.
Tool catalog
All 40 operations are available as REST endpoints and as MCP tools named semuko_*.
Full endpoint reference, scopes and client setup in the developer docs.
Works better together
One platform means fewer tabs, fewer tools, and one source of truth for your business.
FAQ
Straight answers for studios comparing tools or just getting started.
MCP (Model Context Protocol) lets AI assistants call tools. Semuko serves an MCP endpoint at /api/v1/mcp over Streamable HTTP. Each tool maps to a public API operation, and the list is filtered by the scopes on your key or OAuth grant.
Start a free Studio Pro trial, create a scoped key, and connect the tools you already use.