接入你的智能体
发布者自己的命令。不是 PlugMCP 端点。
用我们的密钥与日志托管一份副本。
docker run -i --rm ghcr.io/davidlandais/ovh-api-mcp:0.3.0Claude Code 没有针对本地命令的安装链接。复制下方命令并在终端中运行。
OVH_APPLICATION_KEY=<value> OVH_APPLICATION_SECRET=<secret> OVH_CONSUMER_KEY=<secret> OVH_ENDPOINT=<value> OVH_SERVICES=<value> OVH_CLIENT_ID=<value> OVH_CLIENT_SECRET=<secret> claude mcp add davidlandais-ovh-api-mcp -- docker run -i --rm ghcr.io/davidlandais/ovh-api-mcp:0.3.0在终端中运行。
{ "mcpServers": { "davidlandais-ovh-api-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/davidlandais/ovh-api-mcp:0.3.0" ], "env": { "OVH_APPLICATION_KEY": "<value>", "OVH_APPLICATION_SECRET": "<secret>", "OVH_CONSUMER_KEY": "<secret>", "OVH_ENDPOINT": "<value>", "OVH_SERVICES": "<value>", "OVH_CLIENT_ID": "<value>", "OVH_CLIENT_SECRET": "<secret>" } } }}claude_desktop_config.json
远程 URL 还是本机命令? 两种安装方式的区别
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:
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:
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:
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.
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]
Once connected, the LLM can use the tools like this:
Search for DNS endpoints:
// 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:
// execute tool
async () => await ovh.request({ method: "GET", path: "/v1/domain/zone" })
Get DNS records for a domain:
// execute tool
async () => {
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;
}
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)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
MIT — David Landais
MCP server for the OVH API — explore and execute any OVH endpoint from Claude, Cursor, or any MCP-compatible LLM client. Built in Rust.
{ "mcpServers": { "davidlandais-ovh-api-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/davidlandais/ovh-api-mcp:0.3.0" ], "env": { "OVH_APPLICATION_KEY": "<value>", "OVH_APPLICATION_SECRET": "<secret>", "OVH_CONSUMER_KEY": "<secret>", "OVH_ENDPOINT": "<value>", "OVH_SERVICES": "<value>", "OVH_CLIENT_ID": "<value>", "OVH_CLIENT_SECRET": "<secret>" } } }}工具
暂无工具列表。远程服务器在首次健康检查后会获得工具列表。
常见问题
在本页复制适用于 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 配置。它使用发布者的安装方式,而不是 PlugMCP 代理。
发布者列出了以下环境变量:OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY, OVH_ENDPOINT, OVH_SERVICES, OVH_CLIENT_ID, OVH_CLIENT_SECRET。
Ovh Api 通过 stdio 在本地运行。
上次检查时间:2026-10-28。 MCP server for the OVH API — explore and execute any OVH endpoint from Claude, Cursor, or any MCP-compatible LLM client. Built in Rust.