localstack / localstack/localstack-mcp-server
Inconsistent container name between `lstk` (`localstack-aws`) and MCP (`localstack-main`)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
When running lstk for the first time, it sets up a Docker container named localstack-aws. However, the MCP currently searches for a container named localstack-main by default.
This mismatch can be confusing for new users and makes onboarding harder. It would be helpful to standardize the container name between lstk and the MCP (e.g., both using either localstack-aws or localstack-main), or to document the difference clearly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the lstk first-run container setup and the MCP's default container lookup, then decide whether to standardize on one name or document the difference. Done means the container name is consistent for both paths, or the distinction is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100