Awslabs MCP vs Telbase
A side-by-side look at the Awslabs MCP and Telbase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Awslabs MCP for cloud platforms work as a local process; choose Telbase for cloud platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Awslabs 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Telbase | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 48/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9,821 | — |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Awslabs MCP | View Telbase |
Tools & capabilities
Awslabs MCP tools
No tool names declared yet. Check the project README from the listing page.
Telbase tools
No tool names declared yet. Check the project README from the listing page.
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.
Awslabs MCP
{
"mcpServers": {
"awslabs-mcp": {
"command": "uvx",
"args": [
"awslabs.aws-api-mcp-server@latest"
]
}
}
}
Telbase
No confirmed install command for Telbase yet — follow the setup steps linked from its listing page rather than a guessed package name.