MCP server
Adkumo exposes a Model Context Protocol server, so any MCP client — Claude Code, Claude Desktop, Cursor, ChatGPT — can drive Adkumo without leaving its native chat UI. Search companies, browse ads, list and create creatives, and publish to your connected ad platforms, all from your assistant.
Endpoint
https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp
The exact <project-ref> for your workspace is in your account URL. If you self-host, replace the host with your own.
Authentication
Authentication is OAuth 2.1 — you sign in once with your Adkumo account, the client stores a refresh token, and the connection stays alive. There are no API keys to generate or paste.
The first time you connect a client, your browser opens to the Adkumo login. After you approve, the client gets a short-lived access token plus a refresh token. Refresh happens automatically — you only sign in once.
Plan requirement
The MCP server is available on the Starter plan and above. Any Adkumo account can authenticate and connect — your client shows the server as connected with the full tool list — but on the Free plan every tool call returns a message asking you to upgrade instead of running. Upgrade at app.adkumo.com/settings/billing to unlock the tools.
Connect Claude Code
One command in your terminal:
claude mcp add adkumo \
--transport http \
--url https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp
Claude Code opens a browser tab, you log in to Adkumo, and the connection is live. Verify with claude mcp list.
Connecting from a remote or SSH machine
OAuth opens a browser and redirects to a localhost callback on the machine that runs the client. If Claude Code runs on a remote or SSH box while your browser is on your laptop, that callback can't reach the CLI and the login appears to hang. Two fixes:
- Forward the callback port. Pin it with
claude --callback-port 8765 ..., then from your laptop runssh -L 8765:localhost:8765 <host>and complete the sign-in in your local browser. - Paste the callback URL. If the browser redirect fails after you approve, copy the full callback URL from the browser address bar and paste it into the prompt Claude Code shows.
Connect Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS — adjust the path on Windows / Linux):
{
"mcpServers": {
"adkumo": {
"type": "http",
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp"
}
}
}
Restart Claude Desktop. On first use it opens your browser to sign in, then the Adkumo tools appear in the tool picker on every conversation.
Connect Cursor
Add the same server to ~/.cursor/mcp.json (or a project-level .cursor/mcp.json):
{
"mcpServers": {
"adkumo": {
"url": "https://<project-ref>.supabase.co/functions/v1/mcp-server/mcp"
}
}
}
Reload Cursor and approve the sign-in when prompted.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| 401 Unauthorized on every call | Token expired or revoked — you're signed out | Restart the auth flow: in Claude Code use claude mcp remove adkumo and re-add; in other clients, disconnect and reconnect. |
| Tools reply "upgrade your plan" | Your plan doesn't include MCP access | The MCP server requires the Starter plan or higher. The connection still works, but tools stay locked until you upgrade at app.adkumo.com/settings/billing. |
| 405 Method Not Allowed | The client sent GET / DELETE to /mcp | The transport is stateless and POST-only — usually a client misconfiguration. |
| Tools act on the wrong brand | A different brand is active | Ask the client to switch brands — see Examples. |
Once you're connected, see Examples for the full tool catalog and prompts to try.