Allow passing env vars to stdio MCP tools
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 28
- Avg merge
- 18h 42m
- Merged PRs (30d)
- 16
Description
There is not currently a way to pass environment variables to stdio MCP tools. It might be good to add an additional env parameter to the register_mcp_tools_stdio_async function to allow control of the spawned process' environment. Several tools rely on environment variables for secrets.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating register_mcp_tools_stdio_async and inspect how it spawns the stdio MCP process and constructs its environment. The change is complete when callers can supply an env parameter that controls the spawned process environment, including variables needed for secrets; the issue does not name a test file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100