Cloudforge vs Hostinger API MCP
A side-by-side look at the Cloudforge and Hostinger API MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cloudforge for cloud platforms work as a local process; choose Hostinger API MCP for cloud platforms over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Cloudforge when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cloudforge_diagram_to_mermaid, cloudforge_architecture_summary, cloudforge_mermaid_from_json.
Choose Hostinger API MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
HOSTINGER_API_TOKEN, API_TOKEN, OAUTH_ISSUER, DEBUG. - You want tools like
search, execute, multi-execute.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 55/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | HOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUERDEBUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 164 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 50 | 3 |
| Full listing | View Cloudforge | View Hostinger API MCP |
Tools & capabilities
Cloudforge tools 50
cloudforge_diagram_to_mermaidFetch a saved diagram and render it as an inline Mermaid flowchartcloudforge_architecture_summaryStructured summary: resource counts by category, central components, inline diagramcloudforge_mermaid_from_jsonConvert raw diagram JSON to Mermaid without fetching from the servercloudforge_generate_terraformGenerate Terraform HCL from a natural-language architecture descriptioncloudforge_export_terraform_from_diagramExport Terraform HCL from an existing saved diagram in one stepcloudforge_parse_terraformTurn raw HCL into a diagram structure — deterministic, no AI, **and no account neededcloudforge_export_terraformExport a saved diagram's Terraform as it stands, without regeneratingcloudforge_import_terraformParse existing HCL → diagram structure + Mermaid previewcloudforge_chatAsk the CloudForge AI Architect for IaC advice, cost estimates, security reviewscloudforge_suggest_resourcesGet AI-recommended resources and connections for a described use casecloudforge_list_moldsBrowse 90 curated architecture templates (30 per cloud) — filter by provider, category, or searchcloudforge_get_moldFull detail for one Mold: layout, "why this shape" best practices, inline Mermaid preview, forge link- +38 more on the listing page
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.
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.
Cloudforge
{
"mcpServers": {
"cloudforge": {
"command": "npx",
"args": [
"-y",
"cloudforge-mcp"
]
}
}
}
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"url": "https://mcp.hostinger.com"
}
}
}
Frequently asked questions
Cloudforge is categorized under Cloud Platforms and uses a local stdio subprocess. Hostinger API MCP belongs to Cloud Platforms and uses a remote HTTP/SSE transport. Pick Cloudforge for cloud platforms work and Hostinger API 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.
Cloudforge has no declared pricing — check the project's own site. Hostinger API MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 cloudforge and hostinger-api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cloudforge has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Hostinger API MCP has 57/100 (Good) with 1 views, 0 installs and 164 GitHub stars.