Model Context Protocol

Your assistant,
with the full trail.

Connect supported AI tools to ReasonTrail so they can retrieve approved project context, preserve provenance, and create reviewable captures while you work.

PRIMARY CONNECTION MODE

Connect to
ReasonTrail Cloud.

Coming during private beta

ReasonTrail Cloud MCP

Authenticated HTTPS endpoint

ReasonTrail will provide an authenticated MCP endpoint for supported AI clients. Access will remain bound to your ReasonTrail account, active organization, approved projects, and granted tool capabilities.

Planned server URLhttps://app.reasontrail.ai/mcp

Remote MCP is not available yet. This control will become active during the private beta.

Expected authorization flow

Account and organization scoped
  1. 01

    Sign in to ReasonTrail

  2. 02

    Choose or approve an organization

  3. 03

    Approve requested MCP capabilities

  4. 04

    Connect the AI client

  5. 05

    Review captured or proposed changes

ReasonTrail remains the authorization boundary.

The AI client can request context or actions. ReasonTrail decides what it is authorized to receive or change.

One validated active organization Approved tools and projects Revocable access Membership and suspension rechecked Bounded output No database credentials or provider passwords No browser cookies No unrestricted shell or filesystem access

ReasonTrail does not give models unrestricted database, shell, repository, or filesystem access.

ADVANCED CONNECTION MODE

Developer and
self-hosted local MCP.

Run the ReasonTrail MCP server locally over stdio using your own ReasonTrail installation. This setup is intended for developers, self-hosted deployments, and advanced local environments.

ReasonTrail is the MCP server Codex or Claude is the MCP client No public endpoint is required in local mode
01

Prepare your local installation

Install dependencies and configure the database connection for your self-hosted ReasonTrail instance.

cd /absolute/path/to/reasontrail
npm install
02

Choose your MCP client

Replace the example path with the absolute path to your ReasonTrail installation.

Codex~/.codex/config.toml
[mcp_servers.reasontrail]
command = "npx"
args = ["tsx", "/absolute/path/to/reasontrail/scripts/mcp-server.mts"]
Claude CodeRun in Terminal
claude mcp add reasontrail -- npx tsx /absolute/path/to/reasontrail/scripts/mcp-server.mts
Claude Desktop configuration Show JSON
{
  "mcpServers": {
    "reasontrail": {
      "command": "npx",
      "args": ["tsx", "/absolute/path/to/reasontrail/scripts/mcp-server.mts"]
    }
  }
}
03

Restart the MCP client

The client starts and stops the local ReasonTrail MCP process automatically.

CONNECTED PROJECT MEMORY

Continue working.
Keep the reasoning.

Open ReasonTrail to review what connected clients capture and propose.

Request private beta