Connect a client
The canonical MCP setup for every client. One URL, one OAuth prompt, then start with counts.
Endpoints
| What | URL |
|---|---|
| MCP server (streamable HTTP) | https://mcp.argorant.com/mcp |
| Authorization server metadata | https://mcp.argorant.com/.well-known/oauth-authorization-server |
| Protected resource metadata | https://mcp.argorant.com/.well-known/oauth-protected-resource |
| Connector manifest | https://mcp.argorant.com/manifest.json |
OAuth 2.1 authorization code with PKCE. Clients that cannot be pre-registered self-register at the registration endpoint (dynamic client registration). Refresh tokens are issued.
Per client
| Client | Where | Steps |
|---|---|---|
| Claude | Customize → Connectors → Add custom connector | Paste the URL, sign in. Team and Enterprise: an owner adds it, members connect. Guide |
| ChatGPT | Settings → Security and login → Developer mode → Plugins → + | Name it Argorant, paste the URL under Connection, OAuth. Guide |
| Codex | Plugins | Install the Argorant plugin; it carries the MCP connection and five skills. Guide |
| Custom runtime | Any MCP client with OAuth | Point at the URL, complete the flow, call argorant_account first. |
First calls
argorant_accountshows the connected account, scopes and daily usage.argorant_count_peopleandargorant_preview_peopleare free and safe.- Anything that spends credits or sends email asks the agent to confirm with the user first; the tool descriptions say so and the annotations mark them.
Agents and MCP
A hosted MCP server that lets Claude, ChatGPT, Codex or your own runtime run the whole workflow under your account, scopes and credits.
Claude
Add Argorant to Claude.ai, Claude Desktop or Claude Code. Custom connectors need a Pro, Max, Team or Enterprise plan; Claude Code needs one command.