mcp-server-ovh
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OVH_APP_KEY | No | Application key for API key authentication | |
| OVH_ENDPOINT | No | OVH API endpoint (e.g., ovh-eu) | |
| OVH_CLIENT_ID | No | Client ID for OAuth2 authentication | |
| OVH_APP_SECRET | No | Application secret for API key authentication | |
| OVH_CONSUMER_KEY | No | Consumer key for API key authentication | |
| OVH_CLIENT_SECRET | No | Client secret for OAuth2 authentication |
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 |
|---|---|
| ovh_initialize_clientB | Initialize OVH API client with credentials |
| ovh_oauth2_initializeC | Initialize OVH API client with OAuth2 credentials |
| ovh_requestC | Make a request to OVH API |
| ovh_get_user_infoB | Get current user information |
| ovh_get_billsB | Get user bills |
| ovh_get_servicesC | Get user services |
| ovh_get_payment_methodsC | Get user payment methods |
| ovh_get_ordersC | Get user orders |
| ovh_get_cloud_projectsC | Get cloud projects |
| ovh_get_dedicated_serversB | Get dedicated servers |
| ovh_get_vpsC | Get VPS instances |
| ovh_get_ipsC | Get IP addresses |
| ovh_get_vrackA | Get vRack information |
| ovh_get_load_balancersC | Get load balancers |
| ovh_get_ssl_certificatesC | Get SSL certificates |
| ovh_get_dbaas_logsC | Get DBaaS Logs services |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools target distinct resources (bills, cloud projects, etc.) and are clearly differentiated. However, the generic `ovh_request` tool overlaps with all specific get tools, causing potential confusion for an agent in choosing between them.
All tools follow a consistent `ovh_` prefix. Get tools consistently use `ovh_get_<resource>`, while initialization and request tools use other verbs but still follow the same prefix and underscore pattern, making the naming predictable.
With 16 tools, the server covers a broad set of OVH resources without being overwhelming. This count is well-suited for an API wrapper, providing focused functionality for common operations.
The tool set is heavily skewed toward read-only operations (all get tools) and lacks any specialized write tools (create, update, delete). The generic `ovh_request` tool can fill some gaps but is not a substitute for dedicated CRUD tools. This leaves significant gaps in the expected lifecycle coverage.