Index / MCP servers / Limurse

Limurse MCP server

Limurse is the official remote MCP server from limurse.ai. It answers at https://api.limurse.ai/mcp over streamable HTTP and asks you to sign in with your limurse.ai account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 5 of 5 times since 12 September 2026; the last check, on 19 October 2026, got the sign-in challenge, so it is up.

Status
Answering
Tools
listed after sign-in
Official
yes, served from limurse.ai
Reliability
5 of 5 checks
Response time
905 ms
Transport
streamable HTTP
Last checked
19 October 2026

Find, vet and budget bookable influencers, photographers and videographers for brand campaigns.

Description as the publisher wrote it.

What Limurse needs before it works

A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your limurse.ai account, and the tools appear once you have approved it.

Add Limurse to your AI client

Every block below points at https://api.limurse.ai/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http limurse https://api.limurse.ai/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "limurse": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.limurse.ai/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "limurse": {
      "url": "https://api.limurse.ai/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "limurse": {
      "type": "http",
      "url": "https://api.limurse.ai/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "limurse": {
      "url": "https://api.limurse.ai/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "limurse": {
      "serverUrl": "https://api.limurse.ai/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "limurse": {
      "url": "https://api.limurse.ai/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Limurse
version: 0.0.1
schema: v1
mcpServers:
  - name: Limurse
    type: streamable-http
    url: https://api.limurse.ai/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "limurse": {
      "httpUrl": "https://api.limurse.ai/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "limurse": {
      "type": "http",
      "url": "https://api.limurse.ai/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "limurse": {
      "url": "https://api.limurse.ai/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapi.limurse.ai%2Fmcp&type=streamable_http&id=limurse&name=Limurse

Is Limurse up right now?

It answered our last check on 19 October 2026 in 905 ms. Over 5 checks since 12 September 2026 it answered 5. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Limurse

Questions about Limurse

Is there an official Limurse MCP server?

Yes. It is published by limurse.ai and served from api.limurse.ai, the vendor's own domain: https://api.limurse.ai/mcp.

How do I sign in to Limurse?

Add the server with a setup above. The first time your client connects it opens the sign-in page for limurse.ai; approve it and the tools load.

Is Limurse down?

It answered our last check on 19 October 2026 in 905 ms. Over 5 checks since 12 September 2026 it answered 5.

How do I add Limurse to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.limurse.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Limurse need an API key?

It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.

Where this comes from

Publisher: ai.limurse. Endpoint host: api.limurse.ai. ARD identifier: urn:air:ai.limurse:mcp:limurse. First indexed 12 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.