cloud-mcp
Related Servers
Alternatives to cloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA single STDIO MCP server that provides 48 tools for browser and Chrome DevTools automation, HTTP requests, SQL and MongoDB operations, GitBook, system intelligence, disk management, web search, local transcription, and Ollama delegation, plus runtime connection to external auth-free MCP servers.1MIT
- AlicenseAqualityBmaintenanceAggregates dozens of upstream MCP servers behind a single stdio gateway and lazily loads tool schemas on demand, enabling clients to search, describe, and invoke tools while cutting Turn-0 token usage by 85–95%.4MIT
- FlicenseNot gradedqualityDmaintenanceA cloud replacement for mcp-server-filesystem that provides 30 tools for S3, Azure Blob, and Google Cloud Storage, deployable locally via STDIO or remotely over HTTP/WebSocket with OAuth 2.1 authentication.137 npm3-
- AlicenseBqualityCmaintenanceA local stdio MCP server that provides 69 tools for Cloudflare REST API v4, including DNS, Zones, Workers, KV, R2, D1, Pages, Queues, Tunnels, SSL, WAF, Email Routing, Logpush and Workers AI, authenticated by a single API token.6966 npm3MIT
- AlicenseNot gradedqualityBmaintenanceA remote Streamable HTTP MCP server that lets web clients like Claude.ai and ChatGPT manage cloud machines with OAuth login — creating, starting, pausing and deleting machines, running commands, reading and writing files, managing snapshots and public ports, and driving an optional Linux desktop via screenshots and input actions. Long-running work can be backgrounded and operations polled, so browser-based clients stay within their timeouts.1MIT
- FlicenseNot gradedqualityCmaintenanceMulti-cloud MCP server that exposes cloud AI models as tools for AI CLI agents, supporting streaming, conversation history, parallel multi-model queries, and dynamic model discovery.2-
TDQS
Scored across 5 tools
Each tool targets a distinct step: search discovers operations, describe returns one operation's schema, call executes, providers lists accounts/credentials, catalog writes a file. The only mild overlap is between cloud_search (find operations) and cloud_catalog (enumerate operations into a file), but the output-medium distinction is stated clearly enough.
All names share a consistent cloud_ prefix and snake_case style. However the suffixes mix verbs (search, describe, call) with nouns (providers, catalog), so the verb_noun pattern isn't strictly uniform, though it remains predictable and readable.
Five tools is a tight, well-scoped set for a generic multi-provider API gateway: discover, inspect, invoke, list context, and export. No tool feels redundant and there is no obvious missing piece at this layer.
The search→describe→call pipeline covers the full discovery-to-execution lifecycle, and providers/catalog fill in context and offline grep workflows. Minor gaps remain: no way to set/refresh credentials (only view state) and no built-in pagination or batch handling, though agents can work around these.