René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add dependency injection support to MCPServer","articleBody":"From the V2 checklist in #1253:\n\n\u003e Create dependency injection in `MCPServer`.\n\nMCPServer currently has no built-in mechanism for injecting dependencies (database connections, auth services, configuration objects, etc.) into tool, resource, and prompt handlers. The existing `Context` parameter injection is specific to the MCP request context and does not cover arbitrary user-defined dependencies.\n\nA DI system — similar to FastAPI's `Depends()` — would allow:\n\n- Declaring dependencies as handler parameters that the framework resolves automatically\n- Sharing expensive resources (DB pools, HTTP clients) across handlers without global state\n- Making handlers more testable by swapping dependencies in tests\n- Composing dependencies (dependencies that depend on other dependencies)\n\n### Related but distinct issues\n- #1684 — Refactoring contextvars into explicit parameters (context passing, not general DI)\n- #1695 — Revisiting Context injection mechanism (closed, about the `Context` type specifically)\n\n### Open questions\n- Should this follow FastAPI's `Depends()` pattern exactly, or adapt it for MCP's handler signatures?\n- How does this interact with the `Context` parameter and lifespan state?\n- Should dependencies be scoped per-request, per-session, or per-server?\n\nRef: Kludex's V2 checklist in #1253","author":{"url":"https://github.com/maxisbey","@type":"Person","name":"maxisbey"},"datePublished":"2026-02-13T14:08:20.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2054/python-sdk/issues/2054"}