Connect any MCP client to your product
Any agent that speaks the Model Context Protocol connects to your product through Peeve: Claude, ChatGPT and other OpenAI agents, Hermes, OpenClaw, or an agent you built. The user points it at your scoped Peeve endpoint and it receives your capabilities as typed tools, scoped to that user, with writes confirmed. Nothing about the agent is special-cased; if it speaks MCP, it connects.
- 01Turn on the agent channelThe agent channel is on every Peeve plan. Peeve serves one capability registry to every MCP client, so you define a capability once and it serves both the person and their agent.
- 02Your user gets their endpointEach user has a personal, scoped endpoint, mcp.peeve.ai/<workspace>/u/<contact>, minted per user, revocable by them and visible to you.
- 03They point their agent at itThe user adds that URL in whichever MCP client they run, the same way they would add any custom MCP server, with an access token if their client passes one.
- 04The agent gets typed toolsThe client discovers your capabilities as typed tools with stated effects. Reads run live; writes run only after a confirmation step, inside an allow-list, written to a signed audit log, with exactly that user's permissions.
Which AI agents can connect to my product through Peeve?
Claude, ChatGPT and other OpenAI agents, Hermes, OpenClaw, and any client that speaks MCP. The user points their agent at a scoped Peeve endpoint and it receives your capabilities as typed tools, each stating its effect before it runs. Nothing about the agent is special-cased; if it speaks the protocol, it connects.
What does an agent get when it connects?
Your capabilities, rendered as typed tools with a dry-run effect string, for example change_plan, download_invoice or list_orders. It is the same capability registry that renders as a cursor and narration for a human. You define a capability once and it serves both the person and their agent, never maintained twice.
What permissions does a connected agent have?
Exactly the calling user's permissions, and no more. An agent acting for a user can do what that user can do, nothing they cannot. Each grant is scoped to that user, revocable by them, visible to you and rate-limited per grant, and any state change runs through the same confirmation guardrail as the human path.
Do agent tool calls over MCP cost extra?
No. Agent tool calls over MCP are logged but not billed today. The agent channel is on every plan, with grants limited by plan (5 per user on Starter, 20 on Growth, unlimited on Scale). If the billing model ever changes, you get a full billing cycle's notice, never a retroactive charge.
Related: Peeve over MCP, all integrations, the agent channel, developer docs.