Ovh Api Mcp

io.github.davidlandaisPublished by GitHub account davidlandaisv0.3.0Updated Oct 24, 2026

MCP server for the OVH API. Explore and call any OVH endpoint via sandboxed JS.

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Lets an assistant explore the OVH API specification and call any OVH cloud endpoint by writing sandboxed JavaScript.

What you can do
Exposes two MCP tools: search, which runs JavaScript over the loaded OVH OpenAPI spec to find endpoints, schemas and parameters, and execute, which calls OVH API v1 and v2 endpoints with authentication handled transparently. JavaScript runs in a sandboxed QuickJS engine with memory, stack and timeout limits, and each API call is validated against the spec before execution. It supports stdio and Streamable HTTP transports and caches the merged spec locally.
When to use it
Useful when an assistant needs to inspect or manage OVH cloud resources — DNS zones, domains and other services — through the OVH API, or to discover which endpoints exist before calling them. It is aimed at local development use rather than production or shared deployments.
Requirements
Runs as a local process, via Docker image or pre-built binaries for macOS and Linux. OVH credentials are required for API calls: OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET and OVH_CONSUMER_KEY, or alternatively OVH_CLIENT_ID and OVH_CLIENT_SECRET for OAuth2 service accounts. OVH_ENDPOINT selects the region (eu, ca or us) and OVH_SERVICES limits which services load. Network access to the OVH API is needed.
Before you install
The server holds OVH API credentials (OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY, OVH_CLIENT_SECRET) that can grant broad account access; the README suggests setting all methods including POST, PUT and DELETE on path /* for full access, so scope permissions and validity narrowly. The execute tool can perform write, change and delete operations on OVH resources. It is an early release for local development and should not be exposed to the public internet.

Installation

In SourceWeft

  1. Open Ovh Api Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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).

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.

[ovh-api-mcp MCP server]

How it works

The server exposes two MCP tools:

ToolDescription
searchExplore the OVH OpenAPI spec using JavaScript — find endpoints, inspect schemas, read parameters
executeCall 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:

json
{  "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"      }    }  }}

With Docker

bash
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

From source

bash
cargo install --git https://github.com/davidlandais/ovh-api-mcp
export OVH_APPLICATION_KEY=your_app_keyexport OVH_APPLICATION_SECRET=your_app_secretexport OVH_CONSUMER_KEY=your_consumer_key
ovh-api-mcp --port 3104

Pre-built binaries

Download from GitHub Releases — available for macOS (x86_64, aarch64) and Linux (x86_64 musl).

Claude Code configuration (HTTP mode)

json
{  "mcpServers": {    "ovh-api": {      "type": "http",      "url": "http://localhost:3104/mcp",      "headers": {        "Authorization": "Bearer local"      }    }  }}

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:

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:

VariableDescription
OVH_CLIENT_IDService account ID
OVH_CLIENT_SECRETService 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.

CLI options

Options:  --transport <TRANSPORT>        Transport mode: http, stdio [env: OVH_TRANSPORT] [default: http]  --port <PORT>                  Port to listen on [env: PORT] [default: 3104]  --host <HOST>                  Host to bind to [default: 127.0.0.1]  --endpoint <ENDPOINT>          OVH API endpoint: eu, ca, us [env: OVH_ENDPOINT] [default: eu]  --app-key <APP_KEY>            OVH application key [env: OVH_APPLICATION_KEY]  --app-secret <APP_SECRET>      OVH application secret [env: OVH_APPLICATION_SECRET]  --consumer-key <CONSUMER_KEY>  OVH consumer key [env: OVH_CONSUMER_KEY]  --client-id <CLIENT_ID>        OVH OAuth2 client ID [env: OVH_CLIENT_ID]  --client-secret <CLIENT_SECRET> OVH OAuth2 client secret [env: OVH_CLIENT_SECRET]  --services <SERVICES>          Services to load, comma-separated or "*" [env: OVH_SERVICES] [default: *]  --cache-dir <PATH>             Directory to cache the merged spec [env: OVH_CACHE_DIR]  --cache-ttl <SECONDS>          Cache TTL in seconds, 0 to disable [env: OVH_CACHE_TTL] [default: 86400]  --no-cache                     Disable spec caching entirely  --max-code-size <BYTES>        Maximum code input size [env: OVH_MAX_CODE_SIZE] [default: 1048576]

Usage examples

Once connected, the LLM can use the tools like this:

Search for DNS endpoints:

javascript
// search tool(spec) => {  const results = [];  for (const [path, methods] of Object.entries(spec.paths)) {    if (path.includes("/domain/zone")) {      for (const [method, op] of Object.entries(methods)) {        results.push({ method: method.toUpperCase(), path, summary: op.summary });      }    }  }  return results;}

List your domain zones:

javascript
// execute toolasync () => await ovh.request({ method: "GET", path: "/v1/domain/zone" })

Get DNS records for a domain:

javascript
// execute toolasync () => {  const records = await ovh.request({    method: "GET",    path: "/v1/domain/zone/example.com/record"  });  const details = [];  for (const id of records.slice(0, 10)) {    details.push(await ovh.request({      method: "GET",      path: `/v1/domain/zone/example.com/record/${id}`    }));  }  return details;}

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_secret and consumer_key are stored using secrecy (zeroized on drop)
  • No HTTP redirects — prevents credential leakage to third-party domains
  • Non-root container — Docker image runs as unprivileged user

Architecture

src/  main.rs      CLI, logging, transport selection (HTTP/stdio), graceful shutdown  tools.rs     MCP tool definitions (search, execute) via rmcp macros  sandbox.rs   QuickJS sandboxed JS execution with resource limits  auth.rs      OVH API client with signature, clock sync, request handling  spec.rs      OpenAPI spec fetching, caching, merging, and path validation  types.rs     Input types for MCP tool parameters

License

MIT — David Landais

Source: README.md at commit eb7ac56

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts