Hostinger API MCP vs Edgeone Pages MCP
A side-by-side look at the Hostinger API MCP 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 Hostinger API MCP 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 Hostinger API MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DEBUG, HOSTINGER_API_TOKEN, API_TOKEN, OAUTH_ISSUER. - You want tools like
search, execute, multi-execute.
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 | 52/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | DEBUGHOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUER | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 163 | 440 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Hostinger API MCP | View Edgeone Pages MCP |
Tools & capabilities
Hostinger API MCP tools 3
searchfind operations by keyword; returns each match with its `inputSchema`.executerun one operation: `{ "operation": "<name>", "params": { ... } }`.multi-executerun up to 20 operations in order, stopping at the first failure. A params value that is exactly `"$steps.<i>.<path>"` is replaced by that value from an earlier step's result.
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.
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"command": "npx",
"args": [
"-y",
"@hostinger/mcp"
],
"env": {
"DEBUG": "YOUR_DEBUG_HERE",
"HOSTINGER_API_TOKEN": "YOUR_HOSTINGER_API_TOKEN_HERE",
"API_TOKEN": "YOUR_API_TOKEN_HERE",
"OAUTH_ISSUER": "YOUR_OAUTH_ISSUER_HERE"
}
}
}
}
Edgeone Pages MCP
{
"mcpServers": {
"tencentedgeone-edgeone-pages-mcp": {
"command": "npx",
"args": [
"@edgeone/makers-mcp@latest"
]
}
}
}
Frequently asked questions
Hostinger API MCP 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 Hostinger API MCP 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.
Hostinger API MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 hostinger-api-mcp and tencentedgeone-edgeone-pages-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hostinger API MCP has a quality signal of 52/100 (Good) with 1 views, 0 installs and 163 GitHub stars. Edgeone Pages MCP has 65/100 (Great) with 4 views, 0 installs and 440 GitHub stars.