claude.ai (remote connector)

This is the easiest path and the one the artifact is designed around: both MCP servers are live on Cloudflare Workers, so you connect a URL as a custom connector — no clone, no build, no local process.

Note

Custom connectors are available on claude.ai’s paid plans (Pro / Team / Enterprise) and may be labelled slightly differently per plan. If you don’t see them, use Claude Desktop or Claude Code instead.

Add the connector

1. In claude.ai, open Settings → Connectors → Add custom connector.

2. Paste the server URL (pick a tab below) and save.

3. Start a fresh chat with the connector enabled, and hand it the task.

Rails MCP (operate)

Drives the procurement lifecycle. Token-gated, with a private sandbox per slot:

https://partifact-rails-mcp.thanhvuttv.workers.dev/mcp/<MCP_ACCESS_TOKEN>/<your-slot>

• <MCP_ACCESS_TOKEN> — use the token from your invite (it only gates the endpoint against random traffic).
• <your-slot> — any name you choose ([a-z0-9_-]), e.g. tg-1 or review-3. It’s your own private copy of the Corolla world; change the name any time for a clean slate.

Then, in a fresh chat:

“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.”

See Rails MCP for the full tool list and the slot model.

Docs MCP (read)

Exposes the documentation as tools. Public — no token, no slot:

https://partifact-docs-mcp.thanhvuttv.workers.dev/mcp

Paste it as-is. Sanity-check once connected: ask the agent to run search_docs("verify webhook signature") — it should return the Webhooks page. See Docs MCP.

Sanity-check the endpoint first (optional)

Both servers answer a plain GET / with a liveness line, no token required:

curl https://partifact-rails-mcp.thanhvuttv.workers.dev/
curl https://partifact-docs-mcp.thanhvuttv.workers.dev/

A full MCP handshake on the Rails MCP (needs the token) confirms your slot:

curl -s -X POST "https://partifact-rails-mcp.thanhvuttv.workers.dev/mcp/<MCP_ACCESS_TOKEN>/<your-slot>" \
  -H "accept: application/json, text/event-stream" \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

Connect both

You can add both connectors to the same chat: the Rails MCP to drive the job and the Docs MCP to read the contract while it works. Or connect just one.

Gotchas

• A wrong or missing token on the Rails MCP returns 401 unauthorized.
• Omitting the slot (.../mcp/<token> with no trailing name) drops you in a single shared sandbox — fine for a quick look, but use a slot for an uninterrupted run.
• Each slot holds one supplier credential (Christchurch Toyota), so only orders placed with that supplier can be confirmed — the tools say so, and a capable agent self-corrects if it picks another. A documented demo simplification.