# Agent channel: MCP customer support > Your users' agents connect to a scoped MCP endpoint and get your capabilities as typed tools with stated effects. Canonical: https://peeve.ai/product/agents/ Your users connect their own Claude, OpenAI, Hermes, OpenClaw or custom agent to a scoped MCP endpoint (mcp.peeve.ai//u/) and get your capabilities as typed tools, each stating its effect before it runs. One registry renders as cursor motion for humans and typed tools for agents. Agents get the same permissions as your users, never more. Growth: 5 grants per user; Scale: unlimited. ## More questions ### Can my users' AI agents use Peeve? Yes. Your user connects their own Claude, OpenAI, Hermes, OpenClaw or any MCP client to a scoped Peeve endpoint and gets your capabilities as typed tools, each stating its effect before it runs. Agents get the same permissions as the user, never more, and each grant is revocable and rate-limited. ### Can AI agents use my product on behalf of a customer? This is the emerging surface called agent experience. Peeve lets your users connect their own Claude, OpenAI, Hermes, OpenClaw or any MCP client to a scoped endpoint and get your capabilities as typed tools, each stating its effect before it runs. Agents get the same permissions as the user, never more, and each grant is revocable and rate-limited. ### What is an MCP server for customer support? An MCP server exposes your product's capabilities to AI agents in a standard, machine-readable way. Peeve mints a scoped MCP endpoint per user so an agent acting for that user can call your capabilities as typed tools with stated effects, using the same registry that renders as cursor motion for humans. ### How do I make my product usable by my customers' own AI assistants? You expose your capabilities as tools an agent can call, with permissions and stated effects. Peeve does this from the same capability registry that powers its human-facing cursor, so you define a capability once and it serves both a person and that person's agent, without maintaining two integrations. ### What is agentic commerce or agentic CX, and how do I prepare? It is the shift toward AI agents transacting with products on behalf of people. Preparing means giving agents trustworthy, permissioned, action-ready access to your product. Peeve provides that today: a scoped MCP endpoint where a user's agent gets your capabilities as typed tools, with the same guardrails and confirmation as the human path. ### How is serving AI agents different from serving human customers? Agents need structured actions, explicit permissions, and machine-readable context, not a chat window. Peeve renders one capability registry two ways: cursor motion and narration for people, and typed MCP tools with a dry-run effect string for agents, so both get the same capabilities in the form each can use.