Browse documentation›

DocsAgents & MCPConnect a client

Docs · MCP

Connect a client.

This is the canonical setup for every MCP client. Paste one URL, approve one OAuth prompt, and start with counts. Host-specific pages for Claude and ChatGPT add only the clicks that differ.

1Add the connector URL#

Argorant is a hosted remote MCP server. There is no package to install; if a client asks for package details, give it the manifest endpoints below instead of an npm name.

connector url

https://mcp.argorant.com/mcp

The OAuth flow binds the connector to one Argorant account. Tool access, plan limits, and owner/admin controls all come from that account, and the connector never holds an API key.

Grant types

authorization_code, refresh_token

PKCE

Required (S256)

Client registration

Dynamic, at https://mcp.argorant.com/register

Token endpoint auth

none, client_secret_post

Scopes

argorant:read_counts, argorant:search_segments, argorant:manage_lists, argorant:create_exports, argorant:unlock_contacts

Headless runtimes that cannot be registered by hand can register themselves at the registration endpoint and then run the normal authorization-code flow. What each scope unlocks is on Security & scopes.

3Start with counts and previews#

Size the market before you spend anything. argorant_count_people and argorant_preview_people are free and return aggregates and masked rows; reveal and export are the only tools that draw credits.

first prompt

Count VP Sales contacts at SaaS companies in Germany,
then show me five masked examples before we export anything.

Programmatic access needs a paid plan or purchased credits, see Authentication & limits. The same rate limits apply to MCP traffic as to the REST API.

Discovery endpoints#

Clients that discover auth metadata automatically will find everything from the MCP host. These are also the URLs to hand a directory reviewer.

MCP server URL

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

Path-specific protected resource

https://mcp.argorant.com/.well-known/oauth-protected-resource/mcp

Connector manifest

https://mcp.argorant.com/manifest.json

Well-known manifest

https://mcp.argorant.com/.well-known/argorant-mcp.json

Per-client notes#

The connector URL is identical everywhere. Only the menu path and the prerequisites differ.

Claude

Add a custom connector with the remote MCP server URL. On Team and Enterprise, an owner adds it for the organization first; members connect afterwards.

Settings → Connectors → Add custom connector

Step-by-step Vendor docs

ChatGPT

Developer mode must be on before the connector form appears. Then use the /mcp URL as the server URL.

Settings → Apps & Connectors → Advanced → Developer mode, then Connectors → Create

Step-by-step Vendor docs

Custom agents

Point the client at the server URL and complete the OAuth flow. Clients that cannot be pre-registered can self-register at the registration endpoint.

Remote MCP + OAuth authorization code with PKCE

Vendor docs

Connected?

Read what each tool costs before you let an agent loose on a budget.

Tools reference Security & scopes Create an account

PreviousMCP overview NextTools reference

1Add the connector URL#

2Sign in with Argorant#

3Start with counts and previews#

Discovery endpoints#

Per-client notes#