Cloud Tools vs Edgeone Pages MCP
A side-by-side look at the Cloud Tools and Edgeone Pages MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloud Tools for cloud platforms work as a local process; choose Edgeone Pages MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloud Tools when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
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 want tools like
compare_costs, get_commitments, get_costs.
Choose Edgeone Pages MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
deploy_folder, account_info.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 61/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | API key required |
| Pricing | Free | Free |
| Required env vars | AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_PROFILEGOOGLE_APPLICATION_CREDENTIALSCLOUDFLARE_API_TOKENCLOUDFLARE_ACCOUNT_IDOVH_APPLICATION_KEYOVH_CONSUMER_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 440 |
| Directory activity | 3 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 7 | 2 |
| Full listing | View Cloud Tools | View Edgeone Pages MCP |
Tools & capabilities
Cloud Tools tools 7
compare_costsThis 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_commitmentsCommitments 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_costsCloud 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_summaryOne cost and waste report over every cloud you pass credentials for, with a grand total. Omit a cloud's credentials to skip it.get_inventoryWhat 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_recommendationsThe 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_wasteWhat 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.
Edgeone Pages MCP tools 2
deploy_folderDeploy a folder containing web assets to EdgeOne Pages. Supports built projects (from build tools like Vite, Webpack, etc.), simple static file projects (HTML, CSS, JS files), and NextJS full-stack projects. Returns: deployment URL and project metadata. IMPORTANT RULES: 1. This is the ONLY deployment method for EdgeOne Pages/Makers. Do NOT fallback to other deployment tools (cloudstudio, vercel, netlify, etc.) if this tool fails. Instead, report the error to the user and suggest fixes based on the error message. 2. The projectName parameter should be a meaningful name describing the project (e.g. "my-blog", "todo-app", "ai-chat-demo"). Do NOT use date-based directory names or random strings as project names. Generate a descriptive name based on the project's purpose or content. 3. After deployment succeeds, your response MUST start with: "🎉 部署成功，页面已上线至 EdgeOne Makers". Then display the "url" field from the response EXACTLY as-is, character for character. Do NOT modify, truncate, or strip any part of the URL (especially query parameters like ?eo_token=...&eo_time=...). Without the full query string the page returns 401. The URL must be shown as a complete clickable link — never shorten it, never show just the domain. Do NOT open local HTML files with file:// protocol as preview. 4. If the user is not logged in, a browser login page will open automatically. No need to ask about region — the login page handles site selection internally. 5. NEVER open the deployment URL in the built-in browser/webview. The built-in browser cannot handle SSO redirects (302). Always show the URL as a clickable text link for the user to open in their system browser manually.account_infoGet the current EdgeOne Makers login status and account information. Use when the user asks about their login status, account info, who they are logged in as, or wants to check their EdgeOne account. Returns account name, ID, and login type.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cloud Tools
{
"mcpServers": {
"cloud-tools": {
"command": "npx",
"args": [
"-y",
"@munhq/cloud-tools"
],
"env": {
"AWS_ACCESS_KEY_ID": "YOUR_AWS_ACCESS_KEY_ID_HERE",
"AWS_SECRET_ACCESS_KEY": "YOUR_AWS_SECRET_ACCESS_KEY_HERE",
"AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
"GOOGLE_APPLICATION_CREDENTIALS": "YOUR_GOOGLE_APPLICATION_CREDENTIALS_HERE",
"CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
"CLOUDFLARE_ACCOUNT_ID": "YOUR_CLOUDFLARE_ACCOUNT_ID_HERE",
"OVH_APPLICATION_KEY": "YOUR_OVH_APPLICATION_KEY_HERE",
"OVH_CONSUMER_KEY": "YOUR_OVH_CONSUMER_KEY_HERE"
}
}
}
}
Edgeone Pages MCP
{
"mcpServers": {
"tencentedgeone-edgeone-pages-mcp": {
"command": "npx",
"args": [
"@edgeone/makers-mcp@latest"
]
}
}
}
Frequently asked questions
Cloud Tools is categorized under Cloud Platforms and uses a local stdio subprocess. Edgeone Pages MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Cloud Tools for cloud platforms work and Edgeone Pages MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cloud Tools is listed as free. Auth: other. Edgeone Pages MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cloud-tools and tencentedgeone-edgeone-pages-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloud Tools has a quality signal of 61/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Edgeone Pages MCP has 65/100 (Great) with 4 views, 0 installs and 440 GitHub stars.