Hostinger API MCP vs Synapse RMCP
A side-by-side look at the Hostinger API MCP and Synapse RMCP 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 Synapse RMCP 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 Synapse RMCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
flux, scout.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 52/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | DEBUGHOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUER | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 163 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Hostinger API MCP | View Synapse RMCP |
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.
Synapse RMCP tools 2
fluxDocker daemon, container, host, and Compose operations.scoutSSH/local host inspection, filesystem reads, allowlisted exec,
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"
}
}
}
}
Synapse RMCP
{
"mcpServers": {
"synapse-rmcp-2": {
"command": "npx",
"args": [
"-y",
"@dinglebear/synapse"
]
}
}
}
Frequently asked questions
Hostinger API MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Synapse RMCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Hostinger API MCP for cloud platforms work and Synapse RMCP 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. Synapse RMCP has no declared pricing — check the project's own site. 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 synapse-rmcp-2 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. Synapse RMCP has 55/100 (Good) with 1 views, 0 installs and 2 GitHub stars.