Skip to content

Enterprise deploymentCustomer-hosted or fully managed.Contact salesView pricing

+Integrations · MCP

Intertrace + MCP servers

Put MCP tool calls in the request path for Cursor, Claude and Devin — authorized, pinned and logged.
MCP (Cursor / Claude Desktop) · json
{
  "mcpServers": {
    "intertrace-secured": {
      "url": "https://intertrace.fly.dev/mcp",
      "headers": {
        "Authorization": "Bearer itr_rt_YOUR_RUNTIME_KEY",
        "X-Intertrace-MCP-Server": "YOUR_SERVER_KEY"
      }
    }
  }
}

# Devin (custom HTTP — server key in the URL)
# https://intertrace.fly.dev/mcp?server=YOUR_SERVER_KEY
# Auth Header: Authorization: Bearer itr_rt_YOUR_RUNTIME_KEY

Point Cursor, Claude, or Devin at /mcp. Existing apps keep working; new SDKs skip the handshake.

+Three steps

  1. 01

    Get a runtime key

    Create an itr_rt_* key in Connect. It carries your tenant, so no org headers are needed.

  2. 02

    Point the client at Intertrace

    Paste the snippet. Nothing else in your code changes.

  3. 03

    Watch decisions arrive

    Every call shows up in Traffic with its verdict and the reason, in monitor mode first.

Full setup guide in the docs →

+Watch

MCP servers, connected in 0:20

+What you get

Once it's connected

  • Every tools/call authorized against policy before it reaches the server
  • Tool descriptions inspected for hidden instructions
  • Tool schemas pinned — drift is caught, not trusted
  • Denied calls fail closed with a logged reason

+ The AI watching your AI

Protect your MCP servers agents today.

Start in monitor mode, see every decision, then turn on enforcement when you're ready.