Connect an MCP client

The connection is always per user: the assistant starts acting on behalf of whoever authorized it.

Before you start

1. You need to be logged into the app with the role you want to use.
2. Your administrator needs to have enabled the features you intend to use (accounts, opportunities, campaigns).

Authorization flow

1. In the MCP client, add a remote server and enter https://api.agents2.me/mcp.
2. The client discovers the metadata at /.well-known/oauth-protected-resource and opens the browser.
3. Log into agents2.me (if you aren't logged in yet).
4. The app opens the consent screen showing the name of the client requesting access.
5. Approve or deny.
6. The client receives the tokens and starts listing the tools.

Known clients

Client	How to add
Claude	Settings → Connectors → Add custom connector → paste the endpoint URL
ChatGPT	Settings → Connectors → Create → MCP endpoint URL
Cursor / VS Code	The editor's MCP configuration file, type http, endpoint URL
n8n and automations	Generic MCP client node, type Streamable HTTP, with OAuth

The client needs to support remote MCP over HTTP with OAuth. Clients that only speak local MCP (stdio) require an adapter.

Verify it worked

1. In the app, open Settings → Connected apps.
2. The connection should appear with the client name, the date of last use, and the responsible user.
3. In the assistant, ask something simple — "list my conversations awaiting response".

Usage examples

Request to the assistant	Tools triggered
"What's awaiting response right now?"	list_open_conversations
"Summarize Maria's conversation"	search_inbox + get_conversation_history
"Take her conversation and reply X"	take_conversation + send_message
"Which opportunities closed this month?"	search_opportunities + run_report
"Build the re-engagement campaign for contacts with no contact for 30 days"	create_campaign + list_campaign_templates + update_campaign

Revoke access

In Settings → Connected apps, use the trash icon on the connection's row. The revocation is immediate: that connection's tokens stop working and the assistant needs to authorize again to come back.

Limits

• 120 calls per minute per connection. Exceeding that, the response is 429 and you just have to wait.
• 30 days of refresh token validity. After that, authorize again.
• The connection is personal: two users pointing the same assistant have distinct connections, with distinct permissions.

See OAuth and security for the technical details.