For AI agents: Find a documentation index at https://talkjs.com/llms.txt (full content at https://talkjs.com/llms-full.txt). Get a markdown version of any page by appending .md to its URL path.

TalkJS MCP server

Connect your AI agent to TalkJS so you can configure your project from a conversation.

View as Markdown

Connect your agent to TalkJS

Start here if you have a TalkJS project you can open in the dashboard. If you’re adding chat to your codebase for the first time, follow Agent Skills.

Send your agent this prompt.

Connect to the TalkJS MCP server at https://mcp.talkjs.com/mcp.
Once I’ve signed in, tell me which project I’m connected to and what language its chat UI uses by default.

Follow the agent’s sign-in instructions. In your browser, choose a TalkJS project and approve access. The agent can now work with that project’s test app using your dashboard permissions. If your agent needs you to add the server yourself, follow the manual setup instructions.

Try a change

Once your agent has confirmed the app, try asking:

Set the default chat language to French, then check which language is saved.

Your agent should report fr-FR as the new default. To work on another project, disconnect TalkJS in your agent’s connection settings, then reconnect and choose the other project during sign-in.

Connect manually

Codex CLI

codex mcp add talkjs --url https://mcp.talkjs.com/mcp
codex mcp login talkjs

Claude Code

claude mcp add --transport http talkjs https://mcp.talkjs.com/mcp

Open Claude Code, run /mcp, select talkjs, and follow the sign-in prompt.

Cursor, ChatGPT, and Claude on the web

In Cursor, add a remote server named talkjs with the URL https://mcp.talkjs.com/mcp. Use Streamable HTTP in the Cursor MCP configuration. In ChatGPT or Claude on the web, add the same URL as a custom connector and follow the sign-in prompt. If TalkJS is already configured, open its connection settings.

Tool reference

ToolWhat your agent can do
get_connection_statusCheck whether TalkJS is connected and identify the selected test app.
get_settingsRead the app name, default locale, authentication requirement, and custom fields.
update_settingsChange the name, default locale, authentication requirement, or custom fields.
list_secret_keysList key IDs, creation times, and active status, and see which key signs webhooks.
get_secret_keyLook up a key’s metadata by ID.
create_secret_keyCreate an active key and get its ID.
update_secret_keyActivate or deactivate a key, or choose an active key to sign webhooks.
delete_secret_keyDelete an inactive key that is no longer used for webhooks.

Custom field values are strings. Updates merge with existing fields. A null entry removes that field, and passing null for the entire custom object clears all custom fields. Before asking your agent to require authentication, set up user authentication in your backend.

Secret-key tools return IDs and metadata. If your backend needs the secret value, copy the active key under Settings in the TalkJS dashboard, or run talkjs secret-keys get <id> yourself with the same test app selected in the CLI.