TalkJS is an MCP server published by com.talkjs, hosted at mcp.talkjs.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 8 tools, including create_secret_key, delete_secret_key, get_connection_status, get_secret_key, get_settings.
Let your AI assistant configure and manage TalkJS chat in your app.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs 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.
No parameters.
{
"name": "create_secret_key",
"title": "create_secret_key",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | The full 12-character ID returned by list_secret_keys. |
{
"name": "delete_secret_key",
"title": "delete_secret_key",
"description": "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.",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}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 parameters.
{
"name": "get_connection_status",
"title": "get_connection_status",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| id * | string | The full 12-character ID returned by list_secret_keys. |
{
"name": "get_secret_key",
"title": "get_secret_key",
"description": "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.",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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 parameters.
{
"name": "get_settings",
"title": "get_settings",
"description": "Read basic settings for the connected TalkJS test app. Requires login and settings:read.\nIf authentication is required, show the user the concrete steps for their client:\nConnect your TalkJS account using the steps for your client:\n- Codex CLI: type `/mcp login talkjs` in the active Codex session.\n- Claude Code: type `/mcp`, select the TalkJS server, and follow the authentication prompts.\n- 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.\n- Claude web: open Customize > Connectors, find TalkJS, and click Connect.\n- Cursor: open Customize > MCP, select TalkJS, and follow the sign-in prompt.\n- Other MCP clients: open the TalkJS server's connection settings and choose Authenticate, Sign in, or Connect.\n\n`talkjs` in these commands is the configured MCP server name. Substitute the actual name if it was registered differently.\nComplete browser authorization, choose the TalkJS project's test app, then retry the requested operation.\n\nTerminal alternatives: run `codex mcp login talkjs` for Codex or `claude mcp login talkjs` for Claude Code.\nAfter terminal login, reconnect the MCP server in the active client if it still reports disconnected; start a new agent session if necessary.\n",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}List the connected test app's secret-key IDs, creation times, active status and webhook selection. Returns metadata only.
No parameters.
{
"name": "list_secret_keys",
"title": "list_secret_keys",
"description": "List the connected test app's secret-key IDs, creation times, active status and webhook selection. Returns metadata only.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | 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. |
{
"name": "update_secret_key",
"title": "update_secret_key",
"description": "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.",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}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.
| Parameter | 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 | enum | Whether users must supply backend-generated authentication tokens. |
{
"name": "update_settings",
"title": "update_settings",
"description": "Update the connected TalkJS test app's settings. Supply one or more fields.\nCustom fields merge; a null entry deletes that field, and custom: null clears all custom fields.\nRequiring authentication needs backend-generated user tokens; making it optional permits impersonation.\n",
"inputSchema": {
"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."
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}When disconnected or authentication is required, show the concrete login steps for the user's current client. If unknown, show the client choices below. 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. Use get_connection_status to check the current TalkJS connection. Ask the user to complete login; do not assume a browser flow has started. After login, retry the requested tool. Do not claim they are connected until get_connection_status returns connected: true. Secret-key tools return IDs and metadata only, never secret values. If the user needs a secret value, tell them to view the key in the TalkJS dashboard or manually run `talkjs secret-keys get <id>` in their terminal with the same project selected. Leave secret retrieval to the user; do not run that command yourself or ask them to paste the secret into the chat.
Names, descriptions and schemas were written by the server and are shown as data.