GET:
tools count means you are ready. An
{"error": "not_available"} means one of the preconditions is unmet.
Claude
Add the server in Claude’s connector settings, pointing at your endpoint URL:/u/{contact} URL and
supply the pv_grant_… token as a bearer credential.
Cursor
In~/.cursor/mcp.json (global) or .cursor/mcp.json (per project):
Any MCP client
If your client needs the details spelled out:Verifying by hand
Troubleshooting
tools/list returns an empty array
tools/list returns an empty array
The endpoint is working, but nothing is projected. Every tool must come from
a capability that is in the current production map, verified, marked
agent-accessible, and not disabled. Check those four in the dashboard.A workspace with no production map version at all projects nothing — run the
baseline capture first.
"Agent channel not available for this workspace."
"Agent channel not available for this workspace."
One of: the workspace id is wrong; the agent channel is switched off; the
kill switch is on; the subscription has lapsed. The message is deliberately
the same for all of them, so work through them in that order. The plan is
not one of the causes — the channel is on every plan.
"Invalid or revoked grant token."
"Invalid or revoked grant token."
Per-user endpoint only. The token is missing, malformed, revoked, expired,
or bound to a different contact or workspace than the URL. Check the
Authorization: Bearer header is actually being sent — some clients drop
custom headers silently.429 Rate limited
429 Rate limited
You are above your plan’s ceiling. Honour the
retry-after header. If a
client is polling tools/list, stop — the list does not push changes, and
re-listing on a timer is what usually causes this.The assistant says it completed an action
The assistant says it completed an action
It did not.
tools/call returns guidance only. If an assistant reports
having performed a write through this server, that is the assistant
over-claiming — nothing on the Peeve side executed. See
the overview.