Public MCP for Agent Clients
Planned hosted and package-based MCP surfaces for OpenPermit agent-client adoption.
This page describes planned behavior. The public OpenPermit MCP endpoint and package are not implemented yet. Use the SDK wrapFetch flow today.
OpenPermit MCP should be public in two forms:
- Hosted remote MCP:
https://mcp.openpermit.ai/mcp - Publishable npm package:
@openpermit/mcp
The hosted endpoint is the default for clients such as Codex, Claude Code, desktop assistants, and hosted agent runtimes that can connect to remote MCP servers. The package is for local development, self-hosting, and platforms that need to run the MCP adapter beside the agent runtime.
Planned v1 tools:
paid_fetch: fetch a paid resource through OpenPermit policy and payment execution.quote_resource: discover price and payment method before execution when possible.list_mandates: show scoped mandates available to the connected agent client.get_receipt: retrieve receipt and settlement status.request_manual_approval: start an escalation flow when policy requires human approval.
MCP tool calls will require OAuth or a scoped agent credential bound to one organization and one mandate. Bootstrap tokens and broad service-account keys are not valid agent-client credentials.
The MCP adapter will share the same paid-fetch core as /api/v1/agent/fetch; payment, policy, retry, and receipt behavior should not fork between MCP and HTTP agent paths.