Skip to content

[Bug]: MCPRouter does not forward sandbox environment to stdio servers #8556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
1 task done
cshimmin opened this issue May 17, 2025 · 0 comments
Open
1 task done

[Bug]: MCPRouter does not forward sandbox environment to stdio servers #8556

cshimmin opened this issue May 17, 2025 · 0 comments
Labels
bug Something isn't working mcp Related to MCP functionality

Comments

@cshimmin
Copy link
Contributor

cshimmin commented May 17, 2025 •
edited
Loading

Is there an existing issue for the same bug? (If one exists, thumbs up or comment on the issue instead).

  • I have checked the existing issues.

Describe the bug and reproduction steps

I'm running a few different MCP servers that require some common API keys. Initially I tried exporting these keys to the sandbox environment via [sandbox.runtime_startup_env_vars], but it seems this environment is not picked up by whatever mcpm.MCPRouter is doing. Instead, I have to specify the same environment multiple times as [mcp.stdio_servers.env], which is not ideal.

OpenHands Installation

development mode

OpenHands Version

0.38.0

Operating System

linux
@cshimmin cshimmin added the bug Something isn't working label May 17, 2025
@mamoodi mamoodi added the mcp Related to MCP functionality label May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working mcp Related to MCP functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cshimmin @mamoodi