Limurse MCP server

Limurse publishes a remote Model Context Protocol server. Once connected, an assistant works Limurse's creator marketplace on your behalf, using your own account's access, all the way to a booking. It shortlists creators, budgets with market rate bands and drafts the brief. Then start_booking opens the booking for the creator you chose, where you confirm the brief and pay on Limurse, and get_campaign_results reads back your campaign's governed results: a metric that was not measured stays missing, never estimated.

You stay in control of every booking and payment. The server exposes no tool that publishes, edits or sends anything on its own: no collaboration, no invitation, no status change, no payment. create_brief returns an unsaved draft, and start_booking returns a link for you to open.

Once connected, ask in plain language. For example:

• “Find 10 skincare creators in London with 10K to 100K followers who have worked with beauty brands.”
• “What does a reel from a fitness micro-influencer usually cost? Give me a budget for five of them.”
• “Draft a campaign brief for our summer footwear launch, two reels per creator, English and Spanish.”
• “Then open a booking with the second creator on that list.”

Your assistant picks the right tool, reads public creator profiles and market rate bands, and hands you a Limurse link when you are ready to book. You approve every step that matters on Limurse itself.

Or add this URL as a custom connector wherever your client accepts one:

https://api.limurse.ai/mcp

Your client will open a Limurse consent screen in the browser, where you sign in and approve the access it asked for. Nothing is shared until you approve it, and you can revoke a connection at any time from Settings → Connected apps on Limurse.

• Claude (web, desktop and mobile): Open Limurse in the Claude directory (claude.ai/directory/limurse), choose Connect and sign in to Limurse when asked. The connector then follows you to Claude Code and the Claude mobile apps.
• ChatGPT: Open Settings, then Apps and Connectors, and create a connector with the server URL. Depending on your plan, custom connectors may need developer mode switched on first.
• Claude Code: Run claude mcp add --transport http limurse https://api.limurse.ai/mcp, then /mcp to sign in.
• Cursor, VS Code and other MCP clients: Add the server URL to the client’s MCP server list (the JSON below). Clients that read the official MCP Registry can also find it by name.

For a client configured from a file rather than a UI, the same URL goes in its MCP server list:

{
  "mcpServers": {
    "limurse": {
      "type": "http",
      "url": "https://api.limurse.ai/mcp"
    }
  }
}

The server is published in the official MCP Registry as ai.limurse/limurse. Find it on: Claude directory, Official MCP Registry, Glama.

The server implements OAuth 2.1 with PKCE, and Limurse is the authorization server. It supports dynamic client registration, so most MCP clients can connect without anyone issuing them credentials by hand.

• Protected resource metadata: https://api.limurse.ai/.well-known/oauth-protected-resource
• Authorization server metadata: https://api.limurse.ai/.well-known/oauth-authorization-server
• Scopes: creators:read for creator tools, campaigns:read for unsaved briefs and authorized campaign results. All are read-only; there is no write scope. A third scope, ads:read, appears in the authorization metadata but currently gates no tool.
• Transport: Streamable HTTP on POST /mcp, stateless. The server opens no event stream, so GET /mcp answers 405 by design.
• Protocol revision: 2025-06-18.

Access tokens are short-lived and refresh tokens rotate. Re-using a rotated refresh token revokes the whole chain, so a leaked token stops working rather than quietly persisting.

A connected assistant sees exactly what an anonymous visitor to Limurse's public creator search sees: the same records, the same redactions. Email addresses and phone numbers a creator has typed into their bio or headline are removed before anything reaches your assistant. It does not inherit your workspace's private data unless it grants campaigns:read. With that scope, results are limited to campaigns the connected account can already manage.

• Never exposed: creator email addresses, phone numbers, postal addresses, individual rate cards, collaboration preferences, or any other workspace's data.
• Never written: no tool in this server modifies anything on Limurse;create_brief returns an unsaved object for review.
• Rates are aggregates only. get_rate_benchmarks returns bands across the marketplace, not what any one creator charges.

Data handling is governed by our Privacy Policy, and use of the connector by our Terms and Conditions.

Report a problem with the connector, or ask for access to something it does not yet expose, at apps@limurse.ai. For a suspected security issue, follow our Security Policy instead.