MCP server for the OVH API. Explore and call any OVH endpoint via sandboxed JS.
MCPpedia last refreshed this data
io.github.davidlandais/ovh-api-mcp is an MCP server that MCP server for the OVH API. Explore and call any OVH endpoint via sandboxed JS. Its tool list has not been published yet over stdio and http, requires no API key, and scores 66/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"ovh-api": {
"env": {
"OVH_CONSUMER_KEY": "your_consumer_key",
"OVH_APPLICATION_KEY": "your_app_key",
"OVH_APPLICATION_SECRET": "your_app_secret"
},
"args": [
"--transport",
"stdio"
],
"command": "ovh-api-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
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).
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for GCP environment for interacting with various Observability APIs.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
Azure DevOps boards, repos, pipelines & projects for AI agents — governed.
Manage BlazingCDN from AI agents: CDN zones, cache, metrics, domains, cloud storage and video CDN
MCP Security Weekly
Get CVE alerts and security updates for io.github.davidlandais/ovh-api-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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:
{
"mcpServers": {
"ovh-api": {
"command": "ovh-api-mcp",
"args": ["--transport", "stdio"],
"env": {
"OVH_APPLICATION_KEY": "your_app_key",
"OVH_APPLICATION_SECRET": "your_app_secret",
"OVH_CONSUMER_KEY": "your_consumer_key"
}
}
}
}
docker run -d --name ovh-api \
-e OVH_APPLICATION_KEY=your_app_key \
-e OVH_APPLICATION_SECRET=your_app_secret \
-e OVH_CONSUMER_KEY=your_consumer_key \
-p 3104:3104 \
ghcr.io/davidlandais/ovh-api-mcp:latest
cargo install --git https://github.com/davidlandais/ovh-api-mcp
export OVH_APPLICATION_KEY=your_app_key
export OVH_APPLICATION_SECRET=your_app_secret
export OVH_CONSUMER_KEY=your_consumer_key
ovh-api-mcp --port 3104
Download from GitHub Releases — available for macOS (x86_64, aarch64) and Linux (x86_64 musl).
{
"mcpServers": {
"ovh-api": {
"type": "http",
"url": "http://localhost:3104/mcp",
"headers": {
"Authorization": "Bearer local"
}
}
}
}
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 |