Connect with MCP

ReasonTrail Remote MCP uses authenticated Streamable HTTP. The endpoint is:

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

Generate a scoped Bearer token in Settings → MCP clients. Authorization, organization membership, project access and bounded context are checked on every request.

Run the current HTTP transport command after replacing the placeholder token in your client configuration:

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

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

This shape is suitable for clients that support remote MCP servers, including Cursor, VS Code and Claude Desktop. Follow the client's own current transport naming if it uses a dedicated Streamable HTTP field.

• One validated active organization per token
• Scoped project authorization and revocable credentials
• Bounded context with source and revision provenance
• No database passwords, provider keys or unrestricted shell access

Local stdio is an advanced path for a self-hosted checkout. It is not the primary hosted setup. Use the production Remote MCP endpoint unless you operate the application and database yourself.