A
licenseNot graded
qualityF
maintenanceProvides conversational access to LocalStack AWS services (S3, DynamoDB, Lambda, SQS) through natural language, enabling local cloud infrastructure management without real AWS costs.
MIT
LocalStack MCP Server
Related Servers
Alternatives to LocalStack MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes an OpenAPI catalog as tools for AI agents (e.g., Claude Code, Cursor) to query API endpoints via list_endpoints and get_endpoint tools, enabling interactive API exploration without a browser.15 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides a comprehensive suite of tools for interacting with AWS services like S3, EC2, and Lambda using natural language commands. It enables AI assistants to inspect, manage, and operate AWS resources directly through the Model Context Protocol using your local credentials.15 npm1Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables agents to discover and execute local tools via a Streamable HTTP endpoint using the Groq OpenAI-compatible API.-
- AlicenseNot gradedqualityDmaintenanceExposes Composio tools and actions (Gmail, Linear, etc.) as MCP-compatible tools for language models to interact with in a structured way.28 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceExposes internal tools from agent harnesses (Claude Code, Codex, etc.) as a standard MCP server by intercepting LLM API calls.1MIT
TDQS
B3.2/5.0
Scored across 73 tools
Disambiguation4/5
Most tools have distinct purposes, clearly separated by service prefix and action. The main ambiguity is between kinesis_put_record and kinesis_put_records (singular vs. batch), but descriptions clarify the difference. Overall, tools are well-differentiated and easy to navigate.
Naming Consistency5/5
All tool names follow a consistent 'service_verb_noun' pattern in snake_case. Verbs like list, create, delete, get, put, and others are used predictably across services. Even nuanced variations like ssm_get_parameters_by_path maintain the same style, resulting in a highly uniform naming convention.
Tool Count2/5
With 73 tools, this server is extremely large and exceeds the threshold for a well-scoped set. While it covers many AWS services, an agent would face significant selection overhead. The tool count would be more appropriate if split into smaller, service-focused MCP servers.
Completeness4/5
The server covers core CRUD and lifecycle operations for each included AWS service, including S3, SQS, SNS, EventBridge, Kinesis, DynamoDB, Lambda, Secrets Manager, SSM, and SES. Minor gaps exist (e.g., no S3 copy, no SQS visibility timeout update, no Lambda update), but most essential workflows are supported without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues