MCP Server
Limelight runs a Model Context Protocol (MCP) server so an AI assistant — Claude, or any MCP‑compatible client — can work inside your Limelight brand on your behalf: read your campaigns, leads, and signals, follow creator conversations, and reply to them.
Endpoint
https://mcp.limelighthq.com/mcp
Once connected, you can ask your assistant in plain language — "summarize my unread creator conversations", "which campaigns got the most replies this month?", "draft a reply to this creator" — and it answers using live data from your brand.
How it's secured
- OAuth, not an API key. You connect by logging in to Limelight and approving the connection once — the same login you use for the dashboard. Your assistant never sees a password or a long‑lived key. This is separate from the API keys used for the REST API.
- Scoped to one brand. The connection is bound to the brand you approve. Every request is filtered to that brand on the server — there is no argument, id, or thread a caller can pass to reach another brand's data.
- Brand account required. Your Limelight user must be a member of a brand. If it isn't, the consent screen says so and nothing is shared.
- Paid plan required. MCP is included on the Premium, Enterprise, and Managed plans. On the Signal or self‑serve plan every request is refused with a plan‑upgrade message — see pricing.
- Read‑first. Every tool is read‑only except
send-message, which posts a reply into a conversation you already have access to.
What you can do with it
| Area | Examples |
|---|---|
| Campaigns & content | List your campaigns and creator posts |
| Leads & signals | List leads, lead counts by tab or signal, signal emit stats |
| Conversations | List conversations, read a thread, and send a reply |
| Partners & team | List brand partners and members |
| Payments | List transactions |
| Analytics | Creator‑funnel and signal statistics for your brand |
See Available tools for the full list.
Getting started
- Connect your assistant — a one‑time OAuth approval.
- Ask it to do something with your Limelight data.
On‑demand vs. real‑time
The MCP server answers on demand — your assistant pulls data when you ask. For push delivery — a new lead or a new message the moment it arrives — use Webhooks alongside it.