Ovh Api Mcp
Run the OVH API MCP container so your agent can discover and call OVH endpoints through sandboxed JavaScript with your API credentials.
Overview
OVH API MCP is a MCP server for the Operate phase that lets agents explore and call OVHcloud API endpoints via sandboxed JS and stdio MCP.
What is this MCP server?
- Explore and invoke any OVH API endpoint from the agent via MCP
- Sandboxed JavaScript execution layer for safe, structured API calls
- OCI image ghcr.io/davidlandais/ovh-api-mcp:0.3.0 with stdio transport
- Configurable OVH_ENDPOINT (eu, ca, us) and OVH_SERVICES scope (comma list or *)
- Requires OVH application key, secret, and consumer key—full account API access model
- Server version 0.3.0; OCI identifier ghcr.io/davidlandais/ovh-api-mcp:0.3.0
- Required env: OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY
- Default OVH_ENDPOINT eu; OVH_SERVICES default * (all allowed services)
What problem does it solve?
Manually hunting OVH API docs and crafting signed requests burns agent context and breaks automation when you just need DNS or instance changes.
Who is it for?
Indie devs already on OVH who want MCP-native infra tasks (DNS, cloud resources, account APIs) from their coding agent.
Skip if: Builders on Vercel-only or AWS-only stacks with no OVH account, or teams forbidding broad API consumer keys on developer laptops.
What do I get? / Deliverables
After configuring credentials and the OCI MCP image, your agent can discover and execute OVH API operations within your declared service scope.
- Agent-executed OVH API calls within OVH_SERVICES scope
- Discoverable OVH endpoint exploration without manual doc hopping
- Repeatable infra operations (DNS, cloud resources) from the agent toolchain
Recommended MCP Servers
Journey fit
Operate/infra is the canonical shelf because the server’s core job is living cloud control plane access, not greenfield UI work. Infra subphase matches OVH DNS, VPS, Kubernetes, and billing APIs exposed generically rather than a single app feature.
How it compares
Full OVH API MCP bridge with sandboxed JS, not a single-purpose DNS skill or Hokmah-style codebase graph.
Common Questions / FAQ
Who is OVH API MCP for?
Solo builders and small teams using OVHcloud who want their MCP agent to list and call OVH API endpoints safely within configured limits.
When should I use OVH API MCP?
Use it for provisioning tweaks, DNS updates, service inspection, and scripted cloud operations while building, shipping, or operating on OVH.
How do I add OVH API MCP to my agent?
Pull ghcr.io/davidlandais/ovh-api-mcp:0.3.0, set OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY, optional OVH_ENDPOINT and OVH_SERVICES, and register stdio MCP in your client.