Cloud Tools vs Ovh API MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cloud Tools vs Ovh API MCP
In-depth architectural comparison of the Cloud Tools and Ovh API MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Cloud Tools
Cloud Platforms · Local stdio
Quality: 61/100 (Good) | Auth: other
Ovh API MCP
Cloud Platforms · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Cloud Tools if you need specialized Cloud Platforms tools running via a local process. Choose Ovh API MCP if your workspace requires Cloud Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cloud Tools when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, OVH_APPLICATION_KEY, OVH_CONSUMER_KEY.
You need dedicated capabilities in the Cloud Platforms domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: OVH_APPLICATION_KEY, OVH_APPLICATION_SECRET, OVH_CONSUMER_KEY, OVH_CLIENT_ID, OVH_CLIENT_SECRET, OVH_ENDPOINT, OVH_TRANSPORT, OVH_SERVICES.
Multi-cloud cost, inventory and waste analysis over MCP: AWS, GCP, Cloudflare and OVH.
Code Mode MCP server for the entire OVH API. Two tools (search + execute) give LLMs access to all OVH endpoints via sandboxed JavaScript, using 1,000 tokens instead of thousands of tool definitions.
This period against the same day window of the previous month, so a partial month does not read as a fall. AWS and GCP only. GCP needs credentials.gcp.billing_table.
get_commitments
Commitments you are paying for, and whether you are consuming them, over the last 30 days. AWS: Savings Plans utilisation, coverage of eligible spend, and the saving a further commitment would give. GCP: committed use discounts with their expiry. Not implemented for Cloudflare or OVH, which sell no commitments.
get_costs
Cloud spend. AWS: by service over a date range, from Cost Explorer; pass group_by="data_transfer" for transfer cost by usage type. GCP: by service from the BigQuery billing export, which credentials.gcp.billing_table must name — without it you get budget amounts, not spend. Cloudflare: subscriptions and zone plan costs. OVH: the 6 most recent invoices.
get_cross_cloud_summary
One cost and waste report over every cloud you pass credentials for, with a grand total. Omit a cloud's credentials to skip it.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Cloud Tools is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Ovh API MCP belongs to Cloud Platforms using remote streaming HTTP/SSE transport. Select Cloud Tools when you need capabilities focused on cloud platforms and Ovh API MCP when you require tools for cloud platforms.
Primary tools included: Searches the OVH OpenAPI specification, Executes calls across OVH API v1 and v2, Runs JavaScript in a resource-limited QuickJS sandbox.
What exists. GCP: GCE instances, disks, addresses, snapshots, forwarding rules, GKE clusters with node pools, Cloud SQL, Cloud Functions, Cloud Run, GCS buckets, Cloud NAT, Cloud IDS, Artifact Registry, VPN gateways, subnets, PSC endpoints and Cloud Logging ingestion, with a per-project summary. Cloudflare: zones with plan and price, DNS records split proxied against dns-only, certificates with hosts and expiry, and Workers with invocation counts. OVH: instances and active services with renewal dates and monthly cost. Not implemented for AWS.
get_recommendations
The cloud provider's own optimisation suggestions. GCP: the Recommender API across every zone and region — idle VMs, machine type rightsizing, idle disks and addresses, idle and oversized Cloud SQL. Not implemented for the others; AWS Compute Optimizer is read as part of get_waste instead.
get_waste
What is wasted, with the monthly cost of each finding and the utilisation evidence behind it. AWS: idle and oversized EC2 and RDS measured from CloudWatch CPU series, stopped instances, orphaned volumes and snapshots, unused AMIs and Elastic IPs, idle load balancers and NAT gateways, DynamoDB and ElastiCache, and log groups with no retention. GCP: idle and oversized instances, orphaned disks, unattached addresses, snapshots over 90 days, idle Cloud SQL, GKE clusters with no nodes, Cloud Functions and Cloud Run with no invocations, buckets with no lifecycle rule. Not implemented for Cloudflare or OVH.
Ovh API MCP Tools (6)
Searches the OVH OpenAPI specification
Executes calls across OVH API v1 and v2
Runs JavaScript in a resource-limited QuickJS sandbox
Validates API calls against the OpenAPI specification
Supports HTTP Streamable HTTP and stdio transports