Sciple Platform vs Hostinger API MCP
A side-by-side look at the Sciple Platform 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 Sciple Platform 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 Sciple Platform when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SCIPLE_PLATFORM_URL. - You want tools like
list_aws_accounts, list_cloud_resource_types, query_cloud_resources.
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 | 48/100 · Fair | 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 | SCIPLE_PLATFORM_URL | HOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUERDEBUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 164 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 44 | 3 |
| Full listing | View Sciple Platform | View Hostinger API MCP |
Tools & capabilities
Sciple Platform tools 44
list_aws_accountsList AWS accounts connected to the tenant (account_id, name, AWS number, regions, payer flag)list_cloud_resource_typesList synced resource types + row counts for one AWS service in an accountquery_cloud_resourcesQuery cached rows from any synced AWS resource table (paginated, region filter)list_ec2_instancesSummarize EC2 instances for one account or across all (state/type/id/name/ip)list_environmentsList all environments in the tenant (id, name, slug, group, default flag)create_environmentCreate an environment with optional group assignment and default flagupdate_environmentUpdate an environment's name, description, group, or sort orderdelete_environmentDelete an environment by id (irreversible)list_environment_groupsList environment groups (id, name, slug, AWS account binding)create_environment_groupCreate an environment group with optional AWS account bindinglist_servicesList all services in the tenant catalog (id, name, slug)create_serviceCreate a service in the catalog with kind, language, SCM provider, and repository- +32 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.
Sciple Platform
{
"mcpServers": {
"sciple-platform": {
"command": "uvx",
"args": [
"sciple-mcp"
],
"env": {
"SCIPLE_PLATFORM_URL": "YOUR_SCIPLE_PLATFORM_URL_HERE"
}
}
}
}
Hostinger API MCP
{
"mcpServers": {
"hostinger-api-mcp": {
"url": "https://mcp.hostinger.com"
}
}
}
Frequently asked questions
Sciple Platform 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 Sciple Platform 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.
Sciple Platform 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 sciple-platform and hostinger-api-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sciple Platform has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Hostinger API MCP has 57/100 (Good) with 1 views, 0 installs and 164 GitHub stars.