Hostinger API MCP vs MCP Server Aws Sso
A side-by-side look at the Hostinger API MCP and MCP Server Aws Sso 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 MCP Server Aws Sso 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 MCP Server Aws Sso when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
AWS_SSO_START_URL, AWS_SSO_REGION, AWS_REGION. - You want tools like
aws_sso_login, aws_sso_status, aws_sso_ls_accounts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 52/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | DEBUGHOSTINGER_API_TOKENAPI_TOKENOAUTH_ISSUER | AWS_SSO_START_URLAWS_SSO_REGIONAWS_REGION |
| Verified owner | Community listing | Community listing |
| GitHub stars | 163 | 15 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 3 | 5 |
| Full listing | View Hostinger API MCP | View MCP Server Aws Sso |
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.
MCP Server Aws Sso tools 5
aws_sso_loginInitiate AWS SSO device authorization flow to obtain temporary credentials. This flow works as follows: 1. Generates a unique user verification code and authentication URL 2. Opens a browser to AWS SSO login page (if `launchBrowser: true`) 3. You enter the verification code and complete AWS SSO login 4. Background polling automatically collects and caches the token 5. The cached token is used by other AWS SSO tools **IMPORTANT FOR AI ASSISTANTS**: When the tool returns authentication instructions: - ALWAYS check if a browser window opened automatically - If browser opened: Guide the user to complete authentication - If no browser opened: Instruct user to manually open the URL and enter code - Always provide both the verification code and URL as backup Prerequisites: - AWS SSO must be configured with a start URL and region - Browser access is required for authentication - You must have an AWS SSO account with appropriate permissions Returns: Authentication status, session details, verification code and URLaws_sso_statusCheck current AWS SSO authentication status. Verifies if a valid cached token exists and its expiration time. Does NOT perform authentication - only checks status. If no valid token exists, instructs you to run `aws_sso_login`. Use before calling `aws_sso_ls_accounts` or `aws_sso_exec_command`. Returns: Authentication status, session details, expiration time, next stepsaws_sso_ls_accountsList all AWS accounts and roles accessible through AWS SSO. Provides essential information needed for `aws_sso_exec_command`: - Fetches all accessible accounts with IDs, names, and emails - Retrieves all available roles for each account - Handles pagination internally - Caches account and role information Prerequisites: - MUST first authenticate using `aws_sso_login` - AWS SSO must be configured with a start URL and region Returns: Account list with IDs, names, roles, and session statusaws_sso_exec_commandExecute AWS CLI command using temporary credentials from AWS SSO. Workflow: 1. Verifies valid AWS SSO authentication token 2. Obtains temporary credentials for account and role 3. Executes the AWS CLI command 4. Caches credentials for future use (1 hour) Prerequisites: - MUST first authenticate using `aws_sso_login` - AWS CLI MUST be installed on the system - AWS SSO must be configured Required: `accountId`, `roleName`, `command` Optional: `region` Returns: Execution context, command output, errors, exit codeaws_sso_ec2_exec_commandExecute shell command on EC2 instance via SSM using AWS SSO credentials. No SSH access or inbound ports required. Uses SSM's RunShellScript document. Prerequisites: - MUST first authenticate using `aws_sso_login` - EC2 instance MUST have SSM Agent installed - Instance needs IAM role with AmazonSSMManagedInstanceCore policy - Your role needs `ssm:SendCommand` and `ssm:GetCommandInvocation` permissions Required: `instanceId`, `accountId`, `roleName`, `command` Optional: `region` Returns: Execution context, command output, errors, troubleshooting guidance
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"
}
}
}
}
MCP Server Aws Sso
{
"mcpServers": {
"aashari-mcp-server-aws-sso": {
"command": "npx",
"args": [
"-y",
"@aashari/mcp-server-aws-sso"
],
"env": {
"AWS_SSO_START_URL": "YOUR_AWS_SSO_START_URL_HERE",
"AWS_SSO_REGION": "YOUR_AWS_SSO_REGION_HERE",
"AWS_REGION": "YOUR_AWS_REGION_HERE"
}
}
}
}
Frequently asked questions
Hostinger API MCP is categorized under Cloud Platforms and uses a local stdio subprocess. MCP Server Aws Sso belongs to Cloud Platforms and uses a local stdio subprocess. Pick Hostinger API MCP for cloud platforms work and MCP Server Aws Sso 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. MCP Server Aws Sso is listed as free. Auth: oauth 2.0. 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 aashari-mcp-server-aws-sso 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. MCP Server Aws Sso has 63/100 (Good) with 7 views, 0 installs and 15 GitHub stars.