Skip to main content

🖥 Claude Desktop and Cursor

Claude Desktop and Cursor both read their MCP servers from an mcpServers configuration block, and the Studio gives you one ready to paste. This page will guide you through copying the block, adding your token, placing it in each client and checking that the connection works.

Copying the configuration​

  • Open "API & MCP" in the Studio and find "Connect an MCP client".
  • Find "Claude Desktop / Cursor (mcpServers)" and press "Copy".
  • Replace <your-token> with your API token. See Access tokens to create one.

The block lists a server named "swift-axis-news" with your site's endpoint and an Authorization header. With a placeholder token it looks like this:

{
  "mcpServers": {
    "swift-axis-news": {
      "url": "https://your-site.example/mcp",
      "headers": { "Authorization": "Bearer sxa_xxxxxxxx" }
    }
  }
}

If your configuration already has other servers, add the "swift-axis-news" entry inside the existing mcpServers object rather than pasting a second one.

Setting up Cursor​

  • Open Cursor's MCP settings, or the mcp.json file Cursor uses for MCP servers.
  • Paste the "swift-axis-news" entry into mcpServers and save.
  • Check the server list: Swift Axis should show as connected, with its tools listed.

Cursor can keep MCP servers for every project or for one project only. Prefer the setting for your own user, so the token is not saved in a project folder that others can see.

Setting up Claude Desktop​

  • Open Claude Desktop's settings and find where it keeps MCP servers.
  • Add the "swift-axis-news" entry with the endpoint and the Authorization header, and save.
  • Restart Claude Desktop so it picks up the change.

Claude Desktop's setup screens change between versions. If your version does not accept a server address with a header in its configuration, follow Claude Desktop's own instructions for adding a remote MCP server, and give it the same endpoint and Authorization: Bearer header.

Checking the connection​

Simply ask the agent something read-only, such as "List the topics on Swift Axis". It should call list_topics and answer with your topics. This ensures the token and endpoint are right before the agent changes anything.

If the client reports an error:

  • 401: the token is missing, mistyped, expired or revoked. Check "Tokens" in "API & MCP".
  • A missing scope: the error names the scope the tool needs. Create a token with that scope.
  • 429: too many requests. Wait for the time the error gives, then try again. See Safety and permissions.
tip

The "curl" example on the same screen lists the tools from a terminal. It is a quick way to check that a token works before you blame the client.

Best Practices​

  • One client, one token: name the token after the client, such as "Claude Desktop", so you can revoke it on its own.
  • Start with read and write:content: add publish only when you are ready for the agent to put things live.