Quickstart

Local tools for approved source users

The MCP adapter ships in the private Pro Rout monorepo. It uses Node 24 and the pinned pnpm version. No API key, wallet or account token is required. Package names, tool namespaces and route identifiers keep pro-route; the product name is Pro Rout.

corepack pnpm install --frozen-lockfile
corepack pnpm --filter @pro-route/product-mcp... build
node packages/product-mcp/dist/server.js

The last command starts a stdio server and waits for an MCP client. It does not open an HTTP listener. In your client configuration, use an absolute path to the built server:

{
  "mcpServers": {
    "pro-route-products": {
      "command": "node",
      "args": ["/absolute/checkout/packages/product-mcp/dist/server.js"]
    }
  }
}

First useful request

Ask your client to list tools, then call pro_route_capabilities with an empty object. Read this guide with pro_route_read_doc and {"product":"pro-route","section":"overview"}. Discovering a tool never enables a paused feature or a transaction.

Current account workflow

1. Open Account and sign in with your approved email.
2. Edit your private profile, save it explicitly and reopen it after returning.
3. Use the saved-data download and sign-out controls. A conflict keeps unsaved input; an uncertain sign-out keeps private views closed while you retry.

Email sign-in does not link X, GitHub or Google, and does not prove Solana wallet ownership.

The next identity journey is claim a name → create an Agent → edit → publish and share → return. Agent names and writes stay off until their schema, migration and hosted acceptance gates pass. Public samples never reserve a name.