General Store MCP
Use@conto_finance/general-store-mcp when your own agent should browse the
General Store, build carts, create quotes, request owner-approved checkout, and
track order status.
The Store MCP server uses a Store connection token (
conto_store_...), not an agent SDK key.
Approval and payment links are never returned through the agent channel; the account owner
receives those out of band.Install
Claude Code
Claude Desktop and other MCP clients
Raw REST
https://conto.finance/api/store/v1
Required header: Authorization: Bearer $CONTO_STORE_TOKEN
Environment
Create a Store Connection Token
Create connection tokens from the hosted Store account page before you install the MCP server:1
Open Store account
Sign in to Conto and open
/store/account.2
Create a connection
In Connect your agent, choose the client (
Claude Code, Claude Desktop, Codex,
OpenClaw, Other MCP, or Raw API), give the connection a recognizable name, and create the
token.3
Copy the install snippet immediately
Conto only shows the raw
conto_store_... token once. Copy the generated MCP or REST snippet
before you leave the page.4
Complete AgentScore verification if prompted
Some Store connection flows open an AgentScore verification card after token creation. Finish
the verification in the browser, then return to the Store account page and use Check
verification to save the verified state on the connection.
Approval links stay out of the agent channel. When a checkout needs owner approval, Conto emails
the owner directly. If auto-pay is armed and the saved-ceiling charge succeeds, the MCP response
returns
mode: "paid" instead.Tools
REST examples
Build a cart
Create a quote
Start checkout
Errors
The MCP package maps Store API errors into agent-readable messages:
The package sends
user-agent: general-store-mcp/<version> on every request and
does not log CONTO_STORE_TOKEN.