Connecting a client
Add Chatley to Claude, Cursor, ChatGPT, or any MCP client — sign in once in your browser, with no key to copy.
Connecting Chatley to an MCP client takes one URL and a browser sign-in. Your client registers itself automatically, so there is nothing to create in Chatley first and no key to paste anywhere.
Add the server
Add this as a remote MCP server in your client:
https://mcp.chatley.ai/mcp
Your client will open a browser window. Sign in to Chatley as you normally would, review what the client is asking for, and approve it. The window closes and the connection is live.
If you are already signed in to Chatley in that browser, you will usually be asked only to approve — not to sign in again.
What you are approving
The approval screen names the client that is asking and the Chatley account it will act in. It acts as you: an AI agent connected this way can do what your own role allows, and nothing more. If your Chatley role cannot purchase phone numbers, neither can your assistant.
You can revoke a connection at any time from Integrations & API Keys → Connected apps. Revoking takes effect immediately.
Connect with the least-privileged account that can do the work. If you only want an assistant to read call analytics, connect with a member account rather than an owner one.
Choosing which account you are working in
If you administer several Chatley accounts, tools accept an optional account
parameter so you can target one from a single connection. Ask your assistant to
list the accounts it can see — it will call list_tenants — and then name the
one you mean.
Chatley checks that authority on every call. Naming an account you do not administer is refused, whatever the client sends.
Client notes
Claude and Claude Code — add it as a remote MCP server ("Connectors" in
Claude, or claude mcp add in Claude Code). Reads are approved automatically;
Claude prompts you before anything that changes data.
Cursor — add it under MCP servers in settings. Cursor shows the tool list once the connection completes.
ChatGPT — add it as a connector. Availability depends on your plan.
Anything else — any client that supports remote MCP servers over Streamable HTTP or SSE will work. Point it at the URL above.
If the connection fails
| What you see | What it usually means |
|---|---|
| The browser window never opens | The client is configured for a local (stdio) server. Chatley is a remote server — add it as a URL. |
| Sign-in succeeds but the client shows no tools | The client did not complete the connection. Remove the server and add it again. |
| "Authentication required" on every call | The connection was revoked, or the session expired. Reconnect from your client. |
| A specific tool is missing | Your Chatley role does not carry the permission that tool needs. The tool list reflects what you are allowed to do. |
| A tool answers "not permitted" | Same cause, on an account you targeted explicitly. Check with list_tenants which accounts you administer. |
Every refusal from Chatley carries a reason your client can display. If yours shows only a generic failure, check its own logs for the full response before contacting support.