monacloud-mcp
OfficialRelated Servers
Alternatives to monacloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.13Apache 2.0

ATXP MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceGives AI agents a wallet, email, phone number, and instant access to paid MCP tools including web search, image/video/music generation, email, SMS, voice calls, and code execution.45MIT- FlicenseNot gradedqualityCmaintenanceProvides AI agents with 220+ tools for building websites, sending email, managing contacts, invoicing, databases, automation, and more through a single secure connection. Features hardware-bound authentication and works with Claude Desktop, Claude Code, Cursor, and other MCP-compatible clients.-

@easybits.cloud/mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables AI agents to access EasyBits cloud services through a single MCP endpoint, including sandboxes, web search and extraction, file management, SQL databases, documents, video, and app/website hosting.8-- AlicenseNot gradedqualityDmaintenanceEnables AI agents to register, send/receive email, store encrypted credentials, emit audit events, and query behavioral trust scores via MCP tools.05MIT
- AlicenseAqualityDmaintenanceEnables AI agents to discover, subscribe to, and call paid agent services from the AgentStorefront marketplace directly within MCP-aware clients like Claude or Cursor.430 npmMIT
TDQS
Scored across 135 tools
The set is dominated by duplicate compatibility aliases (vibecloud_* mirroring cloud_*), and several tools overlap in purpose (cloud_services vs cloud_services_list, cloud_whoami/monapay_whoami/monapay_me, agent_deploy/cloud_agent_deploy). An agent cannot reliably choose between canonical tools and their aliases.
Most tools follow a readable snake_case prefix + verb_noun convention (cloud_app_*, monapay_*, mail_*). However, names are not consistent: cloud_services_list vs cloud_services, cloud_vps_create vs cloud_service_start, and aliases like vibecloud_create_vps vs cloud_vps_create create mixed conventions.
135 tools is an extreme number for any MCP server, even after accounting for the many vibecloud_* alias duplicates. The size forces an agent to scan dozens of near-duplicate entries for every task, making the surface impractical.
The payment and email sub-domains have strong coverage (checkouts, QR, webhooks, keys, domains, templates, suppressions). But the cloud resource lifecycle has notable gaps: VPS/databases can be created, started, stopped, and rebuilt but not updated or deleted, and cloud_agent_deploy is only a stub.