Skip to main content
The Interfere MCP server gives your agent access to problems, sessions, releases, and workspace operations. It uses your Interfere account and existing workspace permissions. Both endpoints use Streamable HTTP and OAuth. Choose read-only when the agent only needs to investigate. The server rejects operations that are not explicitly declared read-only on that endpoint, including mutations sent through execute.

​
Connect with a plugin

The Claude Code and Cursor plugins configure the server and include an investigation skill. Use a plugin if you want both the connection and guidance for investigating problems.

​
Connect directly

Add the server from your terminal:
Open /mcp in Claude Code and complete the Interfere sign-in flow. For a read-only connection, use the /mcp/readonly URL instead. See Claude Code’s MCP settings for configuration scopes.
Keep credentials out of MCP configuration files. Sign-in requests interfere:access, user:org:read, and offline_access so the client can access Interfere, select your workspace, and refresh its connection.

​
Ask about your workspace

Give the agent a problem link, surface, or time range:
  • “Investigate errors from the last hour in the checkout surface.”
  • “Show the sessions affected by this problem and the release where it began.”
  • “Compare the investigation’s root cause with the supporting traces.”
The server exposes two tools. search discovers operations and their schemas. execute runs requests against those operations. Agents should inspect the current contract before constructing requests and check each returned HTTP status before using its body. The write-enabled endpoint can change data within your permissions. Ask for a specific change when you want one. An investigation does not require changing problem status or workspace settings.

​
Troubleshooting

The Add MCP option in this documentation site’s contextual menu connects a documentation search server. Use the URLs on this page to connect to your product workspace.