davidlandais/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.
How it works
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:
- **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 Authorization header 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:
| 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 /*.
OAuth2 authentication (service accounts)
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.