Infrawise vs Edgeone Pages MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Infrawise vs Edgeone Pages MCP
In-depth architectural comparison of the Infrawise and Edgeone Pages 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
Infrawise
Cloud Platforms · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Edgeone Pages MCP
Cloud Platforms · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Infrawise if you need specialized Cloud Platforms tools running via a local process. Choose Edgeone Pages MCP if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Infrawise when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Cloud infrastructure analysis for AI coding assistants — detects IaC drift, missing indexes, security gaps, and performance anti-patterns across AWS services and databases. 13 tools, works with Claude Code and Cursor.
An MCP service for deploying HTML content to EdgeOne Pages and obtaining a publicly accessible URL.
Category & Scope
Tools & Capabilities Breakdown
Infrawise Tools (22)
get_infra_overview
Complete snapshot — services, counts, high-severity findings, `configured` flag (data age and per-source status ride the `dataHealth` block on every response)
get_graph_summary
Full infrastructure graph — all nodes, edges, and findings
get_table_schema
Column-level schema for named tables/collections — types, PKs, FKs, indexes, DynamoDB keys/billing mode, cost signal (no row data)
analyze_function
Issues in a specific function — scans, missing indexes, N+1, trigger event shapes, missing IAM permissions; returns every same-named file as a separate match, or bind to one with the optional `file` input; names refused Lambda links and why (`unresolvedLambdas`)
suggest_gsi
Exact GSI config for a DynamoDB table + attribute — names the existing index instead when one already covers 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).
Infrawise is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Edgeone Pages MCP belongs to Cloud Platforms using local stdio subprocess. Select Infrawise when you need capabilities focused on cloud platforms and Edgeone Pages MCP when you require tools for cloud platforms.
API Gateway APIs (REST, HTTP, WebSocket) — routes, HTTP methods, paths, and Lambda integrations
get_topic_details
SNS topics — subscription counts, protocols, and filter policies (required message attributes per subscription)
get_secrets_overview
Secrets Manager — names, rotation status, and key names inferred from code (values never included)
+10 more tools listed on main page
Edgeone Pages MCP Tools (2)
deploy_folder
Deploy 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_info
Get 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.