Agent Rescue Desk Production Triage vs Edgeone Pages MCP
A side-by-side look at the Agent Rescue Desk Production Triage 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.
A
Agent Rescue Desk Production TriageCloud PlatformsRead-only triage for n8n, MCP, webhook, and AI agent workflow production failures.37FairAuth: not declaredVerdict: choose Agent Rescue Desk Production Triage for cloud platforms work; 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?
AChoose Agent Rescue Desk Production Triage when
- You need dedicated capabilities in the Cloud Platforms domain.
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 | A Agent Rescue Desk Production Triage | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 37/100 · Fair | 65/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 440 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Agent Rescue Desk Production Triage | View Edgeone Pages MCP |
Tools & capabilities
Agent Rescue Desk Production Triage tools
No tool names declared yet. Check the project README from the listing page.
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.
Agent Rescue Desk Production Triage
No confirmed install command for Agent Rescue Desk Production Triage yet — follow the setup steps linked from its listing page rather than a guessed package name.
Edgeone Pages MCP
{
"mcpServers": {
"tencentedgeone-edgeone-pages-mcp": {
"command": "npx",
"args": [
"@edgeone/makers-mcp@latest"
]
}
}
}
Frequently asked questions
Agent Rescue Desk Production Triage is categorized under Cloud Platforms and uses an install path we have not confirmed yet. Edgeone Pages MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Agent Rescue Desk Production Triage 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. Agent Rescue Desk Production Triage has no confirmed install command yet — follow its own setup instructions.
Agent Rescue Desk Production Triage has no declared pricing — check the project's own site. 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 agent-rescue-desk-production-triage and tencentedgeone-edgeone-pages-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Rescue Desk Production Triage has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Edgeone Pages MCP has 65/100 (Great) with 4 views, 0 installs and 440 GitHub stars.