modelcontextprotocol / modelcontextprotocol/servers
fresh "mcp-proxy" install failed with "mcp-server-fetch" because of dependencies
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Hi
With a fresh (2026-08-12) $ uv tool install mcp-proxy then $ ~/.local/bin/mcp-proxy --host 0.0.0.0 --port 8931 -- uvx mcp-server-fetch throws dependencies error.
Traceback (most recent call last):
File "/home/cyrille/.local/bin/mcp-proxy", line 4, in <module>
from mcp_proxy.__main__ import main
File "/home/cyrille/.local/share/uv/tools/mcp-proxy/lib/python3.14/site-packages/mcp_proxy/__main__.py", line 23, in <module>
from .mcp_server import DEFAULT_EXPOSE_HEADERS, MCPServerSettings, run_mcp_server
File "/home/cyrille/.local/share/uv/tools/mcp-proxy/lib/python3.14/site-packages/mcp_proxy/mcp_server.py", line 24, in <module>
from .proxy_server import create_proxy_server
File "/home/cyrille/.local/share/uv/tools/mcp-proxy/lib/python3.14/site-packages/mcp_proxy/proxy_server.py", line 11, in <module>
from mcp.server.lowlevel.server import request_ctx
ImportError: cannot import name 'request_ctx' from 'mcp.server.lowlevel.server' (/home/cyrille/.local/share/uv/tools/mcp-proxy/lib/python3.14/site-packages/mcp/server/lowlevel/server.py)
Perhaps some changes occured in "mcp-proxy" ?
Thanks and Regards.
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
Reproduce the failure with uv tool install mcp-proxy and the shown mcp-proxy --host 0.0.0.0 --port 8931 -- uvx mcp-server-fetch command. Start in mcp_proxy/proxy_server.py at the request_ctx import and inspect the installed mcp dependency; done means a fresh install runs without the ImportError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100