Tovanix
MCP 接入
把 Tovanix 帳戶接入支援 MCP 的 AI 用戶端。接入地址 https://tovanix.com/api/mcp/rpc,Streamable HTTP 無工作階段,只接受 POST。
- 認證:Authorization: Bearer <憑證>,也可改用 X-MCP-Key 請求標頭;憑證以 mcp_live_ 開頭,只顯示一次
- 授權:能力預設全部關閉、逐條開啟,tools/list 只回傳開啟的能力;工具名為 tovanix_ 加能力名
- 扣費與不可逆操作需要 totp_code 動態驗證碼,並受單次 / 單日消費上限約束
- 來源 IP 白名單、有效期限、每分鐘 120 次的預設呼叫頻率(最高 600)
- 三個資源(能力目錄、帳戶概覽、平台須知)與三個預設提示(帳戶健檢、消費報告、到期檢查)
- 錯誤碼:401 憑證無效、403 來源或帳戶狀態不允許、405 非 POST、413 請求過大
- 建立憑證前必須閱讀並同意《MCP 接入服務協議》,以你名義發出的內容與操作由你負責
- 除扣費與不可逆操作外,修改回呼位址、公開發文、開啟儲存桶公開存取等關鍵設定同樣需要動態驗證碼;AI 發文、傳客服訊息、寄郵件與即時讀取 Telegram 另有依帳戶計算的頻率上限,貼文與客服訊息還會攔截重複內容,傳給客服的訊息會標註「經 AI 助理傳送」
在各 AI 工具中接入 Tovanix MCP
把 <YOUR_MCP_CREDENTIAL> 換成你在控制台建立的 MCP 憑證。
- Claude Code — 在終端機執行
claude mcp add --transport http tovanix https://tovanix.com/api/mcp/rpc --header "Authorization: Bearer <YOUR_MCP_CREDENTIAL>" - Codex — 設定檔:
~/.codex/config.toml[mcp_servers.tovanix] url = "https://tovanix.com/api/mcp/rpc" bearer_token_env_var = "TOVANIX_MCP_CREDENTIAL" - Cursor — 設定檔:
~/.cursor/mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - GitHub Copilot (VS Code) — 設定檔:
.vscode/mcp.json{ "servers": { "tovanix": { "type": "http", "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer ${input:tovanix-credential}" } } }, "inputs": [ { "type": "promptString", "id": "tovanix-credential", "description": "Tovanix MCP credential", "password": true } ] } - Gemini CLI — 設定檔:
~/.gemini/settings.json{ "mcpServers": { "tovanix": { "httpUrl": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - OpenCode — 設定檔:
~/.config/opencode/opencode.json{ "$schema": "https://opencode.ai/config.json", "mcp": { "tovanix": { "type": "remote", "url": "https://tovanix.com/api/mcp/rpc", "enabled": true, "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Qwen Code — 在終端機執行
qwen mcp add --transport http tovanix https://tovanix.com/api/mcp/rpc --header "Authorization: Bearer <YOUR_MCP_CREDENTIAL>" - Kimi Code CLI — 設定檔:
~/.kimi-code/mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - CodeBuddy Code — 在終端機執行
codebuddy mcp add --scope user --transport http --header "Authorization: Bearer <YOUR_MCP_CREDENTIAL>" tovanix https://tovanix.com/api/mcp/rpc - Qoder CLI — 設定檔:
~/.qoder/settings.json{ "mcpServers": { "tovanix": { "type": "streamable-http", "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Kiro — 設定檔:
~/.kiro/settings/mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Trae — 設定檔:
.trae/mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Trae CN — 設定檔:
.trae/mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Trae CLI — 設定檔:
trae_cli.yamlmcp_servers: - name: "tovanix" url: "https://tovanix.com/api/mcp/rpc" type: "http" headers: Authorization: "Bearer <YOUR_MCP_CREDENTIAL>" - GitHub Copilot CLI — 在終端機執行
copilot mcp add --transport http --header "Authorization: Bearer <YOUR_MCP_CREDENTIAL>" tovanix https://tovanix.com/api/mcp/rpc - Cline — 設定檔:
cline_mcp_settings.json{ "mcpServers": { "tovanix": { "type": "streamableHttp", "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Kilo Code — 設定檔:
~/.config/kilo/kilo.jsonc{ "mcp": { "tovanix": { "type": "remote", "url": "https://tovanix.com/api/mcp/rpc", "enabled": true, "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Continue — 設定檔:
~/.continue/config.yamlmcpServers: - name: tovanix type: streamable-http url: https://tovanix.com/api/mcp/rpc requestOptions: headers: Authorization: Bearer <YOUR_MCP_CREDENTIAL> - Zed — 設定檔:
~/.config/zed/settings.json{ "context_servers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Junie — 設定檔:
~/.junie/mcp/mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Amp — 設定檔:
~/.config/amp/settings.json{ "amp.mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Goose — 設定檔:
~/.config/goose/config.yamlextensions: tovanix: enabled: true type: streamable_http name: tovanix uri: https://tovanix.com/api/mcp/rpc headers: Authorization: "Bearer <YOUR_MCP_CREDENTIAL>" timeout: 300 - Augment (Auggie) — 在終端機執行
auggie mcp add tovanix --transport http --url https://tovanix.com/api/mcp/rpc --header "Authorization:Bearer <YOUR_MCP_CREDENTIAL>" - Factory Droid — 在終端機執行
droid mcp add tovanix https://tovanix.com/api/mcp/rpc --type http --header "Authorization: Bearer <YOUR_MCP_CREDENTIAL>" --no-oauth - Crush — 設定檔:
~/.config/crush/crushrcmcp add tovanix --type http --url https://tovanix.com/api/mcp/rpc --header Authorization "Bearer <YOUR_MCP_CREDENTIAL>" - Warp — 在設定介面中貼上
{ "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } - Windsurf — 設定檔:
~/.codeium/windsurf/mcp_config.json{ "mcpServers": { "tovanix": { "serverUrl": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Claude 網頁 / 桌面版 — 在介面中填寫位址,並新增 Authorization 請求標頭(Bearer + 憑證)
https://tovanix.com/api/mcp/rpc - LM Studio — 設定檔:
mcp.json{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } } - Dify — 在介面中填寫位址,並新增 Authorization 請求標頭(Bearer + 憑證)
https://tovanix.com/api/mcp/rpc - 扣子 Coze — 在介面中填寫位址,並新增 Authorization 請求標頭(Bearer + 憑證)
https://tovanix.com/api/mcp/rpc - n8n — 在介面中填寫位址,並新增 Authorization 請求標頭(Bearer + 憑證)
https://tovanix.com/api/mcp/rpc - 其他支援 MCP 的工具 — 在設定介面中貼上
{ "mcpServers": { "tovanix": { "url": "https://tovanix.com/api/mcp/rpc", "headers": { "Authorization": "Bearer <YOUR_MCP_CREDENTIAL>" } } } }
常見問題
tools/list 回傳空清單怎麼辦?
表示這把憑證還沒有開啟任何能力。到控制台「MCP 接入」裡勾選需要的能力後重新連線即可。
扣費工具一直被拒絕是什麼原因?
檢查三件事:這把憑證的消費上限是否還是預設的 0、帳戶是否開啟了兩步驟驗證、當日額度是否已經用完。
相關頁面: 讓 AI 助理直接打理你的 Tovanix 帳戶 · Tovanix API 文件 · 開發者解決方案
正在載入…