Skip to content

Update server-fetch proxy implementation for httpx 0.28+ #1146

Closed as not planned

Description

@olaservo

Is your feature request related to a problem? Please describe.
Proxy handling was recently added to server-fetch using the deprecated proxies argument from httpx<0.28.0: #816

Describe the solution you'd like
Switch to explicit AsyncClient creation as described here: encode/httpx#3424
That way we can update the httpx dependency to newer versions.

Activity

  1. added
    enhancementNew feature or request
    server-fetchReference implementation for the Fetch MCP server - src/fetch
    on Mar 30, 2025
  2. fat-tire commented on May 2, 2025

    @fat-tire

    I think this is just a matter of changing "proxies" to "proxy" in line 75 and 119 of server.py

    See: encode/httpx#2879 for the httpx change. I don't know why they broke this when they could have been backwards-compatible.

    I can submit the above change as a PR, but since they created it as an incompatible change to httpx, this would break for versions before that change. Still, I do think the newest version of httpx should probably be supported (and I suppose a "smart" invocation could be added to check if proxies is valid and use that).

  3. cliffhall commented on Oct 19, 2026

    @cliffhall
    Member

    Closing: superseded by the v2 release.

    Thank you for reporting this, and apologies for the long wait for a response.

    Since this was filed, the reference servers have been rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers). Each server now runs on v2 of its SDK, and the behavior described here has either been fixed or no longer exists in the same form. The fetch server now builds its client with httpx's proxy= argument, so the deprecated proxies= usage that blocked httpx 0.28+ is gone.

    This is not a judgment on whether the problem was real; it's a consequence of the code it describes having been replaced. This is happening as part of the backlog triage in #4875.

    If this still happens on the v2 release, we'd genuinely like to know. Please open a fresh issue with the version you're running and steps to reproduce, and we'll look at it. Note that this repository accepts contributions as issues rather than pull requests; see CONTRIBUTING.md.

    Thanks for taking the time to report it.

  4. added
    closed-superseded-v2Closed: fixed or made obsolete by the v2 / 2026-07-28 refactor (#4875)
    on Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    closed-superseded-v2Closed: fixed or made obsolete by the v2 / 2026-07-28 refactor (#4875)enhancementNew feature or requestserver-fetchReference implementation for the Fetch MCP server - src/fetch

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions