Schema | ovh-api-mcp

ovh-api-mcp

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`OVH_ENDPOINT`	No	OVH API endpoint: eu, ca, us	eu
`OVH_SERVICES`	No	Services to load, comma-separated or *	*
`OVH_TRANSPORT`	No	Transport mode: http or stdio	stdio
`OVH_CONSUMER_KEY`	No	OVH consumer key
`OVH_APPLICATION_KEY`	No	OVH application key
`OVH_APPLICATION_SECRET`	No	OVH application secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
executeA	Execute JavaScript against the OVH API. Use 'search' first to find endpoints. Your code must be an async arrow function: `async () => { ... }` Available: `declare const ovh: { request(options: { method: "GET" \| "POST" \| "PUT" \| "DELETE"; path: string; query?: Record<string, string \| number \| boolean>; body?: unknown; }): Promise<any>; };` Authentication is automatic. Errors (HTTP >= 400) throw exceptions. Examples: `// List email domains async () => await ovh.request({ method: "GET", path: "/email/domain" })` // List accounts then get details async () => { const accounts = await ovh.request({ method: "GET", path: "/email/domain/example.com/account" }); const details = []; for (const name of accounts.slice(0, 5)) { const d = await ovh.request({ method: "GET", path: `/email/domain/example.com/account/${name}` }); details.push(d); } return details; }
searchA	Search the OVH API OpenAPI 3.1 spec. All configured services are included. The spec is passed as argument to your function. Your code must be a function that receives `spec` and returns a value: `(spec) => { ... }` Types available: interface ParameterObject { name: string; in: "path" \| "query"; required: boolean; description: string; schema: SchemaObject; } interface OperationObject { summary: string; parameters: ParameterObject[]; requestBody?: { content: { "application/json": { schema: SchemaObject } } }; responses: { "200": { content: { "application/json": { schema: SchemaObject } } } }; } declare function yourCode(spec: { paths: Record<string, Record<string, OperationObject>>; components: { schemas: Record<string, SchemaObject> }; }): any; Examples: `// Find account-related endpoints (spec) => { const results = []; for (const [path, methods] of Object.entries(spec.paths)) { if (path.includes("/account")) { for (const [method, op] of Object.entries(methods)) { results.push({ method: method.toUpperCase(), path, summary: op.summary }); } } } return results; }` `// Inspect a model schema (spec) => spec.components.schemas["email.domain.Account"]` `// Get request body for creating an account (spec) => { const op = spec.paths["/email/domain/{domain}/account"]?.post; return { summary: op?.summary, requestBody: op?.requestBody, parameters: op?.parameters }; }`

executeA

Execute JavaScript against the OVH API. Use 'search' first to find endpoints. Your code must be an async arrow function: async () => { ... } Available:

declare const ovh: {
request(options: {
method: "GET" | "POST" | "PUT" | "DELETE";
path: string;
query?: Record<string, string | number | boolean>;
body?: unknown;
}): Promise<any>;
};

Authentication is automatic. Errors (HTTP >= 400) throw exceptions. Examples:

// List email domains
async () => await ovh.request({ method: "GET", path: "/email/domain" })

// List accounts then get details
async () => {
const accounts = await ovh.request({ method: "GET", path: "/email/domain/example.com/account" });
const details = [];
for (const name of accounts.slice(0, 5)) {
const d = await ovh.request({ method: "GET", path: `/email/domain/example.com/account/${name}` });
details.push(d);
}
return details;
}

searchA

Search the OVH API OpenAPI 3.1 spec. All configured services are included. The spec is passed as argument to your function. Your code must be a function that receives spec and returns a value: (spec) => { ... } Types available:

interface ParameterObject {
name: string; in: "path" | "query"; required: boolean;
description: string; schema: SchemaObject;
}
interface OperationObject {
summary: string; parameters: ParameterObject[];
requestBody?: { content: { "application/json": { schema: SchemaObject } } };
responses: { "200": { content: { "application/json": { schema: SchemaObject } } } };
}
declare function yourCode(spec: {
paths: Record<string, Record<string, OperationObject>>;
components: { schemas: Record<string, SchemaObject> };
}): any;

Examples:

// Find account-related endpoints
(spec) => {
const results = [];
for (const [path, methods] of Object.entries(spec.paths)) {
if (path.includes("/account")) {
for (const [method, op] of Object.entries(methods)) {
results.push({ method: method.toUpperCase(), path, summary: op.summary });
}
}
}
return results;
}

// Inspect a model schema
(spec) => spec.components.schemas["email.domain.Account"]

// Get request body for creating an account
(spec) => {
const op = spec.paths["/email/domain/{domain}/account"]?.post;
return { summary: op?.summary, requestBody: op?.requestBody, parameters: op?.parameters };
}

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
No resources

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored 2026-05-04 02:40 across 2 tools

Disambiguation5/5

execute and search have entirely different purposes: execute runs API calls, search explores the API spec. No overlap.

Naming Consistency5/5

Both tools are simple imperative verbs, consistent in style and lowercase. No mixing of conventions.

Tool Count4/5

Only two tools, but the server's design (search + execute) is focused and efficient for its purpose. Slightly minimal but still reasonable.

Completeness5/5

The combination of search (explore spec) and execute (make any API call) covers the full workflow of using OVH APIs. No obvious gaps.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

GitHub Repository

Need Help?

Related Servers