Idea: local "serverless" mode ("phantom-running" state)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
The idea is this: as a user, I might want to run a large amount of MCP servers, which could have a significant memory footprint or even some negative impact on CPU usage/battery life on laptops.
To mitigate this, we could have a serverless/start-container-on-demand mode where a proxy server is always ready to take requests on behalf of an MCP, but the actual container is not always continuously running. Instead, we would start the container on demand, and keep it running for a while, perhaps 30 min. After it's been idle for a period of time, the container can be stopped gracefully, but the proxy server keeps receiving requests, so the MCP will appear to be continuously online.
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, tests, or entry points are named. Start by mapping the existing proxy and MCP container lifecycle, then determine how on-demand startup, graceful stopping, idle timeouts, and request handling should interact. Done would require an agreed design and implementation with tests for the phantom-running behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100