Let your AI assistant configure and manage TalkJS chat in your app.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Create a new active secret key for the connected test app and return its ID and metadata only. Never returns the secret value. Ask the user to view it in the TalkJS dashboard or manually run `talkjs secret-keys get <id>` in their terminal. Creates a new key on every call; at most 10 keys are allowed. Does not change webhook selection.
This tool takes no arguments.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http talkjs https://mcp.talkjs.com/mcp
Create a new active secret key for the connected test app and return its ID and metadata only. Never returns the secret value. Ask the user to view it in the TalkJS dashboard or manually run `talkjs secret-keys get <id>` in their terminal. Creates a new key on every call; at most 10 keys are allowed. Does not change webhook selection.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}Permanently delete an inactive secret key that is not selected for webhooks, from the connected test app. Deactivate it first; select a replacement if it is the current webhook key.
| Argument | Type | Description |
|---|---|---|
| id* | string | The full 12-character ID returned by list_secret_keys. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The full 12-character ID returned by list_secret_keys."
}
}
}Check whether this request is connected to a TalkJS test app. No login is required. When disconnected, returns concrete login instructions to show the user for their client.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}Get a secret key's ID and metadata for the connected test app. Never returns the secret value. To view it, ask the user to open the key in the TalkJS dashboard or manually run `talkjs secret-keys get <id>` in their terminal.
| Argument | Type | Description |
|---|---|---|
| id* | string | The full 12-character ID returned by list_secret_keys. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The full 12-character ID returned by list_secret_keys."
}
}
}Read basic settings for the connected TalkJS test app. Requires login and settings:read. If authentication is required, show the user the concrete steps for their client: Connect your TalkJS account using the steps for your client: - Codex CLI: type `/mcp login talkjs` in the active Codex session. - Claude Code: type `/mcp`, select the TalkJS server, and follow the authentication prompts. - ChatGPT web: use the Connect/Sign in prompt shown for the TalkJS tool. If no prompt appears, open the TalkJS plugin's connection settings and connect your account. - Claude web: open Customize > Connectors, find TalkJS, and click Connect. - Cursor: open Customize > MCP, select TalkJS, and follow the sign-in prompt. - Other MCP clients: open the TalkJS server's connection settings and choose Authenticate, Sign in, or Connect. `talkjs` in these commands is the configured MCP server name. Substitute the actual name if it was registered differently. Complete browser authorization, choose the TalkJS project's test app, then retry the requested operation. Terminal alternatives: run `codex mcp login talkjs` for Codex or `claude mcp login talkjs` for Claude Code. After terminal login, reconnect the MCP server in the active client if it still reports disconnected; start a new agent session if necessary.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}List the connected test app's secret-key IDs, creation times, active status and webhook selection. Returns metadata only.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}Activate/deactivate a test app secret key or select it for webhooks. Supply active and/or usedForWebhooks as booleans. Select an active replacement before unselecting or deactivating the current webhook key. Returns metadata only.
| Argument | Type | Description |
|---|---|---|
| id* | string | The full 12-character ID returned by list_secret_keys. |
| active | boolean | Whether the key is valid for authentication. |
| usedForWebhooks | boolean | Select an active key for webhook signing, replacing the current selection. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "The full 12-character ID returned by list_secret_keys."
},
"active": {
"type": "boolean",
"description": "Whether the key is valid for authentication."
},
"usedForWebhooks": {
"type": "boolean",
"description": "Select an active key for webhook signing, replacing the current selection."
}
}
}Update the connected TalkJS test app's settings. Supply one or more fields. Custom fields merge; a null entry deletes that field, and custom: null clears all custom fields. Requiring authentication needs backend-generated user tokens; making it optional permits impersonation.
| Argument | Type | Description |
|---|---|---|
| name | string | App name; trimmed and must not be empty. |
| custom | any | Custom fields to merge. Values are strings or null to delete; null for the whole field clears all custom fields. |
| defaultLocale | string | Locale, for example en-US or pl; normalized by TalkJS. |
| authentication | any | Whether users must supply backend-generated authentication tokens. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"name": {
"type": "string",
"description": "App name; trimmed and must not be empty."
},
"custom": {
"oneOf": [
{
"type": "object",
"additionalProperties": {
"oneOf": [
{
"type": "string"
},
{
"const": null
}
]
}
},
{
"const": null
}
],
"description": "Custom fields to merge. Values are strings or null to delete; null for the whole field clears all custom fields."
},
"defaultLocale": {
"type": "string",
"description": "Locale, for example en-US or pl; normalized by TalkJS."
},
"authentication": {
"enum": [
"required",
"optional"
],
"description": "Whether users must supply backend-generated authentication tokens."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 18, 2026.