
Ovh Api Mcp
io.github.davidlandais由 GitHub 帳號 davidlandais 發布v0.3.0更新於 Oct 24, 2026
MCP server for the OVH API. Explore and call any OVH endpoint via sandboxed JS.
概覽
讓助理透過撰寫沙箱化 JavaScript 來探索 OVH API 規格,並呼叫任意 OVH 雲端端點。
- 可以做什麼
- 提供兩個 MCP 工具:search 在已載入的 OVH OpenAPI 規格上執行 JavaScript,用來尋找端點、結構與參數;execute 呼叫 OVH API v1 與 v2 端點,並透明處理身分驗證。JavaScript 在具備記憶體、堆疊與逾時限制的 QuickJS 沙箱中執行,每次 API 呼叫在執行前都會對照規格進行驗證。支援 stdio 與 Streamable HTTP 傳輸,並在本機快取合併後的規格。
- 適用情境
- 適合助理需要檢視或管理 OVH 雲端資源(例如 DNS 區域、網域及其他服務),或在呼叫前先了解有哪些端點可用時使用。它鎖定本機開發用途,而非正式環境或共用部署。
- 執行需求
- 以本機程序方式執行,可使用 Docker 映像或 macOS、Linux 的預先建置二進位檔。呼叫 API 需要 OVH 憑證:OVH_APPLICATION_KEY、OVH_APPLICATION_SECRET 與 OVH_CONSUMER_KEY,或改用 OAuth2 服務帳號的 OVH_CLIENT_ID 與 OVH_CLIENT_SECRET。OVH_ENDPOINT 選擇區域(eu、ca 或 us),OVH_SERVICES 限定載入哪些服務。需要連線至 OVH API 的網路存取。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Ovh Api Mcp,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
ovh-api-mcp
[CI] [License: MIT] [Rust] [MCP] [Status]
A native Model Context Protocol (MCP) server that gives LLMs full access to the OVH API (v1 and v2). Built in Rust for minimal footprint (~19 MB Docker image, ~1.2 MiB RAM).
[ovh-api-mcp MCP server]Early Release — Designed for local development use. Security hardening has been applied (sandboxed execution, spec validation, secret protection), but the server has not been battle-tested at scale. Do not expose it to the public internet. Feedback and bug reports are welcome.
How it works
The server exposes two MCP tools:
The LLM writes JavaScript that runs inside a sandboxed QuickJS engine with resource limits (memory, CPU timeout, stack size). Every API call is validated against the loaded OpenAPI spec before execution.
The server supports two transport modes:
- HTTP (Streamable HTTP) — for web-based clients and Docker deployments
- stdio — for direct integration with Claude Desktop, Cursor, and MCP inspectors
OVH credentials are optional at startup: the server starts and exposes its tools even without API keys. Tools return a clear error when called without credentials.
Quick start
With stdio (Claude Desktop / Cursor)
Add to your MCP client configuration:
With Docker
From source
Pre-built binaries
Download from GitHub Releases — available for macOS (x86_64, aarch64) and Linux (x86_64 musl).
Claude Code configuration (HTTP mode)
The
Authorizationheader is required to bypass Claude Code's OAuth discovery. See claude-code#2831.
OVH credentials
You need three values: an application key, an application secret, and a consumer key.
Go to the token creation page for your region, log in with your OVH account, set the permissions and validity, and you'll get all three keys at once:
For full API access, set all four methods (GET, POST, PUT, DELETE) with path /*.
OAuth2 authentication (service accounts)
As an alternative to API keys, you can use OVH service accounts with OAuth2 client credentials:
Service accounts are created via the OVH API (POST /me/api/oauth2/client with flow: CLIENT_CREDENTIALS). You must then create an IAM policy (POST /v2/iam/policy) to grant API permissions to the service account. See the OVHcloud documentation for details.
The server auto-detects the auth mode from environment variables. Do not set both API keys and OAuth2 credentials at the same time.
CLI options
Usage examples
Once connected, the LLM can use the tools like this:
Search for DNS endpoints:
List your domain zones:
Get DNS records for a domain:
Security
- Sandboxed execution — JavaScript runs in QuickJS with memory limit (64 MiB), stack limit (1 MiB), and execution timeout (10s for search, 30s for execute)
- Spec-validated API calls — every
ovh.request()call is matched against the loaded OpenAPI spec; unknown endpoints or wrong HTTP methods are rejected - Path injection prevention — API paths containing
?,#, or..are rejected - Secret protection —
app_secretandconsumer_keyare stored usingsecrecy(zeroized on drop) - No HTTP redirects — prevents credential leakage to third-party domains
- Non-root container — Docker image runs as unprivileged user
Architecture
License
MIT — David Landais
來源:README.md,提交 eb7ac56
工具
0版本歷史
1- v0.3.0最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分