Tovanix
讓 AI 助理直接打理你的 Tovanix 帳戶
透過 MCP(Model Context Protocol)把 Tovanix 帳戶接入 Claude 等 AI 用戶端,用一句話完成查餘額、對帳單、續約伺服器、看收款這類操作。
- 涵蓋全部 10 大業務及帳戶、驗證與平台設定,共 500 多項能力,每項能力由你逐條開啟,新建立的憑證預設一項都不開放
- 扣費與不可逆操作必須附上你兩步驟驗證 App 裡的 6 位動態碼,AI 拿不到這個碼,只能向你索取
- 每把憑證單獨設定單次與單日消費上限(預設 0,平台天花板 2000 美元),實際扣款不會高於你確認的金額
- 可限定來源 IP、設定有效期限,每把憑證預設每分鐘 120 次呼叫
- MCP 憑證與開放 API 金鑰相互獨立,刪除即失效,不影響已在運作的整合
- 建立憑證前必須閱讀並同意《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>" } } } }
常見問題
AI 會不會在我不知情的情況下花錢?
不會。扣費類操作同時受三道限制:必須附上你兩步驟驗證 App 裡當下的動態碼;不能超過這把憑證的單次與單日上限;實際扣款不會高於你確認過的金額。憑證的消費上限預設為 0。
支援哪些 AI 用戶端?
支援 Streamable HTTP 傳輸並能設定請求標頭的 MCP 用戶端都可以接入,包括 Claude Code、Codex、Cursor、GitHub Copilot、Gemini CLI、OpenCode、Qwen Code、Kimi Code CLI、CodeBuddy、Qoder、Kiro、Trae、Windsurf 等。伺服器相容 2025-06-18、2025-03-26、2024-11-05 三個協定版本。
相關頁面: MCP 配套技能包:讓 AI 用對你的 Tovanix 帳戶 · MCP 接入 · 開發者解決方案 · Tovanix API 文件
正在載入…