ReasonTrail Remote MCP

Give compatible AI clients the project context they need.

Use authenticated Streamable HTTP to retrieve bounded, source-linked context and submit governed capture requests. ReasonTrail remains the authorization boundary.

Production endpoint

https://app.reasontrail.ai/api/mcp

Create a scoped token in Settings → MCP clients, then add the endpoint to your client.

Copy command

https://app.reasontrail.ai/api/mcp

Scoped organization and project accessBounded context with provenanceRevocable Bearer tokensNo database passwords or provider keys

Claude Code

Connect over HTTP

Copy command

claude mcp add --transport http reasontrail https://app.reasontrail.ai/api/mcp \
  --header "Authorization: Bearer <your-mcp-token>"

Generic clients

JSON configuration

Copy command

{
  "mcpServers": {
    "reasontrail": {
      "url": "https://app.reasontrail.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-mcp-token>"
      }
    }
  }
}

Supported paths

Use the client you already have.

Codex
Claude Code
Claude Desktop
Cursor
VS Code
Other MCP-compatible clients

Authorization boundary

Context is scoped before it leaves ReasonTrail.

Membership, project access, token expiry, privacy policy and bounded output are checked per request. The Runtime and client do not receive unrestricted shell or host filesystem access.

Protocol 3 · Runtime 0.3.3 is the current verified CLI bundle.

Advanced / self-hosted

Local stdio remains available for operators.

Self-hosted deployments can run the local server over stdio, but hosted customers should use Remote MCP. See the connection guide for the boundary and troubleshooting steps.