Rust MCP server exposing OVH API v1 and v2 through searchable, sandboxed JavaScript execution.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Ovh API MCP.
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).
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.
The server exposes two MCP tools:
| Tool | Description |
|---|---|
search | Explore the OVH OpenAPI spec using JavaScript — find endpoints, inspect schemas, read parameters |
execute | Call any OVH API endpoint using JavaScript — authentication is handled transparently |
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:
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.
Add to your MCP client configuration:
Download from GitHub Releases — available for macOS (x86_64, aarch64) and Linux (x86_64 musl).
The
Authorizationheader is required to bypass Claude Code's OAuth discovery. See claude-code#2831.
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:
| Region | URL |
|---|---|
| Europe | https://auth.eu.ovhcloud.com/api/createToken |
| Canada | https://auth.ca.ovhcloud.com/api/createToken |
| US | https://auth.us.ovhcloud.com/api/createToken |
For full API access, set all four methods (GET, POST, PUT, DELETE) with path /*.
As an alternative to API keys, you can use OVH service accounts with OAuth2 client credentials:
| Variable | Description |
|---|---|
OVH_CLIENT_ID | Service account ID |
OVH_CLIENT_SECRET | Service account secret |
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.
Once connected, the LLM can use the tools like this:
Search for DNS endpoints:
List your domain zones:
Get DNS records for a domain:
ovh.request() call is matched against the loaded OpenAPI spec; unknown endpoints or wrong HTTP methods are rejected?, #, or .. are rejectedapp_secret and consumer_key are stored using secrecy (zeroized on drop)MIT — David Landais
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/davidlandais-ovh-api-mcp)<a href="https://allmcps.com/mcp/davidlandais-ovh-api-mcp"><img src="https://allmcps.com/api/badge/davidlandais-ovh-api-mcp?style=directory" alt="Ovh API MCP on AllMCPs" /></a>