ReasonTrail for Teams is now available

Connect AI tools

Connect with MCP

Use the production ReasonTrail Remote MCP endpoint from Codex, Claude, Cursor, VS Code, or another compatible client.

Remote MCP

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

Copy command
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.

An account-scoped connection follows your live access across organizations. Use list_organizations and select_organization to change company without replacing the token. Project-limited credentials remain available for stricter client access.

Claude Code

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

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

Generic JSON configuration

Copy command
{
  "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.

Boundaries

  • One selected organization per request, switchable only among the user's live memberships
  • Current project/team authorization plus any explicit token restriction
  • Bounded context with source and revision provenance
  • No database passwords, provider keys, project-secret reveal or unrestricted shell access

Organizations, Resources and credentials

If a project is missing, call list_organizations, select the intended company, then call list_projects. Organization membership alone does not expose every private project.

upload_markdown_resources adds repository-free Markdown in bounded batches with version history. For credentials, call begin_project_secret_enrollment and enter the value only on ReasonTrail's authenticated page; the model can request an approved exact use but can never reveal the value.

Self-hosted / local stdio

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.