Configure an MCP client
Connect compatible assistants without embedding production credentials.
Endpoint
Use the platform MCP URL. A local platform uses http://localhost:5100/api/mcp.
Claude Code
Set M0_BASE_URL from the quickstart, then run:
claude mcp add --transport http mandate0 "$M0_BASE_URL/api/mcp"In Claude Code, open /mcp, select mandate0, and choose Authenticate. Review the consent screen and approve sandbox access. Then list tools.
A project configuration can use an HTTP mcpServers.mandate0 entry with your actual platform URL. JSON does not expand shell variables unless your client explicitly supports it; do not paste a literal $M0_BASE_URL into the URL field.
Claude.ai and ChatGPT
Use the client's current custom remote-MCP controls, where supported by your plan and workspace. Enter a name and the platform MCP URL. When dynamic registration is supported, leave manually supplied OAuth client credentials blank and complete browser authentication.
Menus and availability change independently of mandate0. Consult the client's official instructions if current controls differ. This guide does not claim a public connector-directory listing.
Codex
Add a remote HTTP MCP server using the configuration supported by your Codex installation, then complete OAuth. Use the same endpoint and sandbox flow. See the official Codex MCP documentation for current configuration syntax.
Verify
List tools, then call m0_list_merchants with { "limit": 5 }. Read-only tools alone can be the intended result of your approved scopes. Keep tokens out of shared configuration, screenshots and prompts.