One endpoint. 14 tools. One API key.
Two ways to connect:
Remote HTTP — For clients that support custom HTTP headers (some VS Code MCP extensions, OpenCode). Point to https://api.talocode.site/mcp with Authorization: Bearer $TALOCODE_API_KEY.
Local Bridge — For clients that do not support custom headers (Claude Desktop, Cursor standard config). Use npx @talocode/mcp as a local stdio bridge. The bridge reads TALOCODE_API_KEY from the environment and forwards requests to the remote endpoint.
Talocode MCP exposes all Talocode Cloud product APIs through the Model Context Protocol. AI coding agents can call Talocode capabilities as MCP tools using a single TALOCODE_API_KEY.
Endpoint: POST https://api.talocode.site/mcp
Auth: Authorization: Bearer $TALOCODE_API_KEY.cursor/mcp.json:
{
"mcpServers": {
"talocode": {
"url": "https://api.talocode.site/mcp",
"headers": {
"Authorization": "Bearer ${TALOCODE_API_KEY}"
}
}
}
}claude_desktop_config.json:
{
"mcpServers": {
"talocode": {
"url": "https://api.talocode.site/mcp",
"headers": {
"Authorization": "Bearer ${TALOCODE_API_KEY}"
}
}
}
}Use when your MCP client cannot send custom HTTP headers.
Works with Claude Desktop, Cursor, OpenCode:
{
"mcpServers": {
"talocode": {
"command": "npx",
"args": ["@talocode/mcp"],
"env": {
"TALOCODE_API_KEY": "tk_live_xxxxxxxxxxxx"
}
}
}
}
The bridge forwards all requests to https://api.talocode.site/mcp
with Authorization: Bearer $TALOCODE_API_KEY.| Tool | Product | Est. Credits |
|---|---|---|
| tera_writing_rewrite | Tera | 5 |
| tera_writing_draft | Tera | 10 |
| tera_coding_explain | Tera | 10 |
| tera_coding_review | Tera | 20 |
| router_chat | Router | Variable |
| agent_browser_check | Agent Browser | 5 |
| agent_browser_screenshot | Agent Browser | 8 |
| agent_browser_trace_report | Agent Browser | 15 |
| cliploop_brief_generate | ClipLoop | 15 |
| cliploop_script_generate | ClipLoop | 15 |
| cliploop_video_render | ClipLoop | 200 |
| cliploop_campaign_create | ClipLoop | 50 |
| cliploop_campaign_package | ClipLoop | 400 |
| cloud_pricing | Cloud | Free |
MCP tool calls are billed as standard Talocode Cloud API requests. Credits are deducted from your wallet. No separate MCP billing.
Never commit API keys to configuration files. Use environment variable substitution (${TALOCODE_API_KEY}) where supported. Talocode MCP never logs raw keys and redacts authorization headers.