Claude Desktop

Claude Desktop can reach the servers two ways: remote (the deployed Workers — nothing to build) or local (the stdio servers running on your machine). Remote is simplest; local is good for development and needs no token.

Where the config lives

macOS    ~/Library/Application Support/Claude/claude_desktop_config.json
Windows  %APPDATA%\Claude\claude_desktop_config.json

Edit it, save, and fully restart Claude Desktop to pick up changes.

Option A — Remote (deployed, no build)

On paid plans, the simplest route is the connectors UI, identical to the web app: Settings → Connectors → Add custom connector, then paste the URL. See claude.ai for the exact URLs.

If you’d rather wire it through the config file, bridge the remote Streamable-HTTP server to stdio with mcp-remote:

{
  "mcpServers": {
    "partifact-rails": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://partifact-rails-mcp.thanhvuttv.workers.dev/mcp/<MCP_ACCESS_TOKEN>/<your-slot>"
      ]
    },
    "partifact-docs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://partifact-docs-mcp.thanhvuttv.workers.dev/mcp"]
    }
  }
}

Replace <MCP_ACCESS_TOKEN> with the token from your invite and <your-slot> with any name. Keep only the server(s) you want.

Option B — Local (stdio, no token)

The stdio servers run the mock in-process — one self-contained install, no deployment, no token, no slot (each reseeds per process). Build them once:

1. Clone the repo and install:

   git clone https://github.com/vutran-tvg/prototype-rails-agentic
   cd prototype-rails-agentic
   pnpm install

2. Build the server(s) you want:

   pnpm --filter @partifact/mcp-rails build   # → packages/mcp-rails/dist/stdio.js
   pnpm --filter @partifact/mcp-docs build    # → packages/mcp-docs/dist/stdio.js

3. Point the config at the built entrypoints (absolute paths):

   {
     "mcpServers": {
       "partifact-rails": {
         "command": "node",
         "args": ["/abs/path/to/prototype-rails-agentic/packages/mcp-rails/dist/stdio.js"]
       },
       "partifact-docs": {
         "command": "node",
         "args": ["/abs/path/to/prototype-rails-agentic/packages/mcp-docs/dist/stdio.js"]
       }
     }
   }

4. Restart Claude Desktop. The tools appear under the 🔌 connector menu.

Skip the build during development

To iterate without a build step, run the server directly with tsx — set "command": "pnpm", "args": ["--filter", "@partifact/mcp-rails", "dev"]. Use an absolute-path node dist/stdio.js for a stable install, since Desktop spawns the command from its own working directory.

Then hand it the task

Open a fresh conversation and, for the Rails MCP:

“Using only the Rails MCP tools, take the 2019 Toyota Corolla job (CCC-2026-04817) through to a reconciled invoice, and tell me what you did at each step.”

The agent orients itself from get_started / guide://lifecycle / scenario://current alone. For the Docs MCP, ask it to search_docs("verify webhook signature") as a smoke test.