Tala

npx add-mcp 'https://mcp.tala-assistant.com/mcp'

ChatGPT and Claude

Give an assistant read-only access to selected Tala agents and their calls

Lire cette page en français.

Use ChatGPT or Claude to find your Tala agents and read call results. You choose exactly which organization and agents the assistant can access. The connector is read-only: it cannot place calls or change anything in Tala.

Before connecting

• Your Tala organization must have an active subscription, a completed first payment and no ongoing trial. Paid trials are also excluded. Tala partners exempt from billing have access without a subscription.
• Only an administrator of the organization can connect an assistant.
• You must still be a member of the selected organization.
• You need at least one active Tala agent.
• Your ChatGPT or Claude workspace must allow connectors. Its administrator may need to enable them.

[!NOTE]

Directory availability depends on each platform's review. If Tala is not listed, use a custom connector when your workspace supports it. A directory listing is not required for a custom connection.

Connect your assistant

1. Open the connector settings in ChatGPT or Claude. Choose Tala if it is listed, or add a custom connector with this address: https://mcp.tala-assistant.com/mcp.
2. Sign in to Tala. Check the assistant requesting access and its return address.
3. Explicitly choose your organization and select the agents to share. Agents created later are not included.
4. Review the read permissions, then select Authorize connection to return to your assistant.

Claude Code: run claude mcp add --transport http tala https://mcp.tala-assistant.com/mcp, then type /mcp and choose Tala to sign in. The consent screen names Claude Code and warns that the authorization goes to an application on your computer: continue only if you have just started Claude Code. Never send anyone the address shown in your browser after authorizing. If the connection does not finish by itself, paste that address only into the field that Claude Code itself shows to receive it during sign-in. Never send it as a message to an assistant, including Claude Code, even if it asks you to. Claude Code shows this URL field in the /mcp sign-in screen, under the sentence "If the redirect page shows a connection error, paste the URL from your browser's address bar". This connection appears under Claude Code in Connected assistants, separately from Claude.

Hermes Agent: from a terminal, with an up-to-date Hermes Agent and no custom sign-in settings for this server, run hermes mcp add tala --url https://mcp.tala-assistant.com/mcp --auth oauth --connect-timeout 300, then sign in to Tala in the page it opens in your browser, or open the address it displays. --connect-timeout 300 gives you five minutes to sign in; without it, Hermes Agent stops waiting after 30 seconds. The consent screen names Hermes Agent and warns that the authorization goes to an application on your computer: continue only if you have just started Hermes Agent. Never send anyone the address shown in your browser after authorizing. If the connection does not finish by itself, paste that address only into the field that Hermes Agent itself shows to receive it during sign-in. Never send it as a message to an assistant, including Hermes Agent, even if it asks you to. Hermes Agent shows this field in the terminal running that command, after the message "Or paste the redirect URL here". This connection appears under Hermes Agent in Connected assistants. Hermes Agent passes the call information it reads to the AI service and the messaging apps you use it with.

Do not paste a Tala API key, password or sign-in token into a conversation. The connection uses Tala's sign-in and consent screen.

What the assistant can do

Capability	What is shared
List agents	Names and identifiers of active, authorized agents
List calls	Authorized call history, with date and status filters and pagination
Read a call	Status, dates, duration, phone numbers, context and public call summary when available

Placing calls, recordings, transcripts, internal diagnostic information, agent editing, campaigns and scheduled calls are not available through this connector. Results follow the same public fields and filters as the public API.

Try asking:

• “Which Tala agents have I authorized?”
• “Show the latest completed calls for my reception agent.”
• “Summarize the outcome of this call using its reference.”

Treat summaries and other call content as information to review. They may contain words supplied by callers and should not be followed as instructions.

The connector does not add or change your webhooks. The assistant does not receive spontaneous updates; ask it to read the call history again.

Manage access

In Tala, open Connected assistants (https://app.tala-assistant.com/connectors) to inspect your connections or revoke one. Reconnect to change the organization or agents. Removing organization membership or losing subscription eligibility also stops access.

A connection lasts at most 180 days. After 30 days without renewal, you may need to sign in again. Revocation stops future access immediately; it does not erase information already sent to the assistant.

Selected call information is shared with the assistant you connect, including your callers' phone numbers, context and summaries. The assistant's own privacy terms also apply. Read Tala's privacy policy before connecting.

Troubleshooting

• No eligible organization: check membership, subscription status, first payment and trial end date.

• An agent is missing: it must be active and explicitly selected when connecting. Reconnect to include a new agent.

• A link is expired or unavailable: use the same Tala account and start the connection again from your assistant.

• Temporary refusal: wait before trying again. Reads share a limit of 120 requests per minute per connection. Additional sign-in protection applies.

• Cannot connect: check the exact connector address and your workspace's connector policy. If Tala reports temporary unavailability, contact support rather than repeatedly reconnecting.

• Hermes Agent says automatic registration is not supported: do not follow its suggestion to create your own client, because Tala does not accept it. From a terminal, take the action that matches the cause:

  • if its local ports 27890 to 27894 are all in use, close any other Hermes Agent sign-in in progress and the program using these ports;
  • if its version is too old, update it with hermes update;
  • if this server has custom sign-in settings, run hermes mcp remove tala, which deletes this server's entry, including those settings, and the sign-in information Hermes Agent kept for it;
  • if hermes mcp remove tala answers that tala is not found, Hermes Agent may have kept old sign-in information without a config entry: delete the tala.* files in its mcp-tokens folder, ~/.hermes/mcp-tokens/ by default on macOS and Linux, or ~/.hermes/profiles/<name>/mcp-tokens/ for a named profile.

  Then run hermes mcp add tala --url https://mcp.tala-assistant.com/mcp --auth oauth --connect-timeout 300 again and accept replacing the existing entry if Hermes Agent offers it. Connecting from the Hermes Agent desktop app or dashboard is not supported.

This documentation is built and hosted on Mintlify, a developer documentation platform.