Skip to main content

MCP server setup

Connect Claude Desktop, Claude Code, Cursor or VS Code to your organization through the Trace.Space MCP server, with a browser sign-in and no API keys.

Written by Karlis Broders

The Trace.Space MCP server lets an external AI assistant such as Claude Desktop, Claude Code, Cursor, or VS Code read and update your organization's data. MCP (Model Context Protocol) is the standard these tools use to connect to external services. Once connected, the assistant can do the same things the built-in Space Agent can, from your own tool.

The server URL

The URL depends on where your Trace.Space account is hosted:

  • Europe: https://api.tracespace.app/core/mcp

  • North America: https://api.tracespace.ai/core/mcp

Org admins can always find the right URL for their instance on the Integrations page described below.

Connecting from the Integrations page

If you are an org admin, go to Organization settings > Integrations and find the MCP Server box. It shows the MCP server URL with a copy button, and a Download for client button that generates a ready-made config file for:

  • Cursor - save as ~/.cursor/mcp.json

  • VS Code - save as .vscode/mcp.json in your project

  • Claude Code - save as .mcp.json in your project

Each entry in the menu also has a copy icon if you prefer to paste the JSON into an existing file. The generated config names the server trace-space and pins it to your current organization, so the assistant always works in the right org.

The MCP Server box on the Integrations page

After saving the file, restart or reload your client. On first use it opens a browser window where you sign in to Trace.Space and allow the connection. This is a standard OAuth login, so there are no API keys to create or store. If your client shows a stale-session error after a Trace.Space release, reconnect once.

Connecting from Claude Desktop

  1. In Claude Desktop, open Customize, then the Connectors tab, and click + to add a custom connector.

The Connectors tab in Claude Desktop with the + menu open on Add custom connector

  1. Type a name, for example Trace.Space MCP, and paste the server URL for your region (see above).

The Add custom connector dialog with the name Trace.Space MCP and the server URL filled in

  1. Click Add. You may need to click Connect, sign in to Trace.Space in the browser, and allow the browser to open Claude Desktop to establish the connection.

The Trace.Space MCP connector listed in Claude Desktop with a Connect button

Once the connection succeeds, the Trace.Space MCP tools are listed as in the screenshot below, and you can use them in your chats.

The connected Trace.Space MCP connector in Claude Desktop listing its tools under Tool permissions

Optional: use API client credentials. For a smoother sign-in in Claude Desktop you can add an API client from your Trace.Space organization.

  1. In Trace.Space go to Organization settings > Integrations, create a new API client, give it a name and click Create API Client.

The New API Client dialog in Trace.Space with a name entered

  1. Copy the Client ID and Client Secret into Advanced settings of the connector in Claude Desktop.

The API Client Credentials dialog showing the Client ID and the Client secret field (secret hidden) with copy buttons
The Add custom connector dialog in Claude Desktop with the client ID and secret entered under Advanced settings

  1. Click Add in Claude Desktop. The Trace.Space tools appear as before.

What the assistant can do

The server exposes 30 tools that let the assistant read, create, update and move items, follow traces, filter and search, manage item types and picklists, read parameters, baselines and reviews, record review feedback, and read the activity feed. Every tool is listed in the MCP tools reference.

The assistant acts with your permissions, so it can only see and change what you can.

Did this answer your question?