Campaign discovery
Search live campaigns by category, city, budget, creator type and timing — the same index that powers the public campaign board, without scraping a single page.
An open Model Context Protocol server for CastersApp. Ask about campaigns.popular areas.live traffic.creator reach. Answers come from live records, not a stale export.
Works with Claude Desktop · Claude Code · Cursor · any MCP client
Drop the server into your client's MCP config. No SDK, no build step, no local database.
{ "mcpServers": { "casters": { "command": "npx", "args": ["-y", "@casters/mcp-server"], "env": { "CASTERS_API_KEY": "sk_live_..." } } } }
$ claude mcp add casters \ --env CASTERS_API_KEY=sk_live_... \ -- npx -y @casters/mcp-server # verify it registered $ claude mcp list
{ "mcpServers": { "casters": { "url": "https://mcpserver.castersapp.com/sse", "headers": { "Authorization": "Bearer sk_live_..." } } } }
One question, one tool call, an answer built from live rows.
| Kesän hauskimmat tuliaiset | 4,182 views |
| Weekend Festival 2026 | 3,067 views |
| Syksyllä uusi harrastus | 2,415 views |
Typed, documented and scoped to the caller's own permissions.
Search live campaigns by category, city, budget, creator type and timing — the same index that powers the public campaign board, without scraping a single page.
Pull creator profiles with follower counts, categories, cities and portfolio links across Instagram, TikTok, YouTube and Facebook — normalised into one shape.
List, review, accept or reject applications programmatically — with the same guardrails the dashboard enforces.
Reach, impressions, engagement and conversion per campaign or creator, aggregated on the server so your context stays small.
Every call is bound to an API key. A brand key never sees another brand's data — enforced server-side, not by prompt.
Create a scoped API key from your Casters dashboard. Brand, creator and read-only scopes are issued separately.
Paste the config above into your MCP client and restart it. The server advertises its tools automatically on handshake.
“Which active beauty campaigns in Helsinki still have open slots?” Your assistant calls the right tool and answers from live data.
The Model Context Protocol is an open standard for connecting AI assistants to external systems. Instead of pasting data into a chat, the assistant calls typed tools directly — so answers come from live records rather than a stale copy.
Every request is authenticated with a scoped API key and authorised server-side against the same rules as the web dashboard. Keys are revocable at any time, and write operations are opt-in per key.
Anything that speaks MCP — Claude Desktop, Claude Code, Cursor, and custom clients built on the MCP SDKs. Both stdio and HTTP/SSE transports are available.
The server is included with your Casters account. Rate limits apply per key and scale with your plan.
Generate a key and connect in a minute. No migration, no SDK, no lock-in.