MCP server

The Model Context Protocol (MCP) is an open standard that lets an AI assistant call outside tools. Rixe runs an MCP server, so an assistant such as Claude Desktop or Cursor can answer questions like "which prompts are we invisible in on Perplexity?" from your live Rixe data, right where you are already working, without opening the dashboard.

The server uses the same API keys and scopes as the REST API. Each tool asks for its own scope, so a key can be limited to exactly what the assistant should see.

#Where to find it

Open the user menu at the bottom of the sidebar and go to Settings › Developer. The MCP server card shows the Server URL, a Client config (Claude Desktop / Cursor) snippet, a Quick test command and the list of tools, each with a Copy button.

MCP access comes with the "REST API + MCP" feature: you need a plan that can create API keys. See Plans and limits.

#Set it up

1. In Settings › Developer › API keys, click Add API key, name it (for example "Claude Desktop") and tick the scopes for the tools you want (see the table below). Click Generate key and copy it; it is shown only once.
2. Copy the Client config snippet from the MCP server card into your client's MCP configuration. For Claude Desktop that is claude_desktop_config.json; for Cursor, its MCP settings file.
3. Replace rixe_… with your key and restart the client.

The snippet uses the mcp-remote bridge, which runs through npx (Node.js must be installed):

{
  "mcpServers": {
    "rixe": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.rixe.ai/mcp",
        "--header",
        "Authorization: Bearer ${RIXE_API_KEY}"
      ],
      "env": { "RIXE_API_KEY": "rixe_YOUR_KEY" }
    }
  }
}

4. Ask the assistant something like "Using Rixe, list my workspaces and summarise visibility for the first one." It should call calisma_alanlari first, then gorunurluk_ozeti.

#Quick test from the command line

curl -s https://api.rixe.ai/mcp \
  -H 'Authorization: Bearer rixe_YOUR_KEY' -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A working key returns {"jsonrpc":"2.0","id":1,"result":{"tools":[…]}}.

#Tools

Tool names are fixed identifiers (they happen to be Turkish words); your assistant reads the English description of each and picks the right one. Every tool except calisma_alanlari needs a workspaceId. Where days is accepted, the default window is 30 days and the maximum is 180.

#Calling a tool directly

The server answers the MCP methods initialize, ping, tools/list and tools/call. A tool result is a single text block containing JSON:

curl -s https://api.rixe.ai/mcp \
  -H 'Authorization: Bearer rixe_YOUR_KEY' -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"calisma_alanlari","arguments":{}}}'

{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "[\n  {\n    \"id\": \"9b1f6c2e-4d1a-4f0e-8a51-2f3c7d9e1a10\",\n    \"name\": \"FlowCRM – US\"\n  }\n]"
      }
    ]
  }
}

#Errors

• No key or a revoked key: the HTTP request itself fails with 401, before any JSON-RPC reply.
• Missing scope, unknown tool or missing argument: the HTTP status is 200 and the reply carries a JSON-RPC error with code -32603, for example This API key is missing the "read:actions" scope or query is required. Tools the key can use keep working; only the one call fails.

#Limits and good to know

• The server is stateless: there are no sessions, streaming or server-initiated messages. Each call is a single request and response.
• It shares the API's rate limit of 1,200 requests per minute.
• The data is the same as in the app: scores follow the daily measurement, and a rate built on fewer than 4 measurements is marked as not enough data rather than given as a number.
• MCP is read-only apart from asistan, which spends money but does not change your data.

#Related pages

• REST API: keys, scopes and rate limits in detail.
• Assistant
• Brand kit and knowledge base
• Action plan