Setup - Talqing

The server runs locally over stdio (npx -y @talqing/mcp, Node 20 or newer) and calls the Talqing API with your personal access token. The dashboard’s Agents page has a Build agents from your terminal panel with these commands pre-filled for Claude Code, Codex and Grok; Copy copies the real token even while it is masked. Any personal access token works too.

Environment variables

Variable	Value
`TALQING_BASE_URL`	`https://api.talqing.com`
`TALQING_API_KEY`	Your personal access token, sent as `Authorization: Bearer <token>`

Both are required and have no default. If either is missing, the server exits at startup and prints the variable’s name.

Client configuration

claude mcp add talqing \
  -e TALQING_BASE_URL=https://api.talqing.com \
  -e TALQING_API_KEY=$TALQING_API_KEY \
  -- npx -y @talqing/mcp

codex mcp add talqing \
  --env TALQING_BASE_URL=https://api.talqing.com \
  --env TALQING_API_KEY=$TALQING_API_KEY \
  -- npx -y @talqing/mcp

# ~/.grok/config.toml — `grok mcp add` takes no --env flag
[mcp_servers.talqing]
command = "npx"
args = ["-y", "@talqing/mcp"]
env = { TALQING_BASE_URL = "https://api.talqing.com", TALQING_API_KEY = "<personal access token>" }

{
  "mcpServers": {
    "talqing": {
      "command": "npx",
      "args": ["-y", "@talqing/mcp"],
      "env": {
        "TALQING_BASE_URL": "https://api.talqing.com",
        "TALQING_API_KEY": "<personal access token>"
      }
    }
  }
}

Cursor reads this from .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project.

Pin a version

npx -y @talqing/mcp fetches the latest release each time the client starts it. To pin, use @talqing/mcp@x.y.z in args, or install globally and point the client at the talqing-mcp binary:

npm install -g @talqing/mcp

{
  "mcpServers": {
    "talqing": {
      "command": "talqing-mcp",
      "env": {
        "TALQING_BASE_URL": "https://api.talqing.com",
        "TALQING_API_KEY": "<personal access token>"
      }
    }
  }
}

Verify

Restart the client and ask “List my Talqing agents.” It should call list_agents and return your agents, or say there are none. Both mean the connection works.

Troubleshooting

The server does not appear or does not connect

Check claude mcp list or codex mcp list. Client configuration is often per project, so a server added in one directory may be missing in another.Run the server by hand to see startup errors:

TALQING_BASE_URL=https://api.talqing.com \
TALQING_API_KEY=$TALQING_API_KEY \
npx -y @talqing/mcp

A healthy start prints nothing and waits on stdin; press Ctrl-C. A missing variable prints its name and exits.

401 invalid token

The token was truncated when pasted (copy it again with Copy), it was revoked (revocation takes effect on the next call), or TALQING_BASE_URL is not the API host. A 403 means the token works but your role does not allow the operation — see permissions.

Tools are missing, or the context fills up

The server registers about 160 tools. Some clients cap the number of tools across all servers; disable MCP servers you are not using and reconnect. Tool definitions carry only a one-line summary and fetch arguments on demand (tools), but keeping one task per session still helps.An operation that never appears is one that is not exposed; permissions lists them.

Recipes

Prompts that build, run and debug end to end.

Tools

How a tool maps to its HTTP call.

​Environment variables

​Client configuration

​Pin a version

​Verify

​Troubleshooting

​Next