You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, I have multiple streamable MCP services, and deploying them is using too many server ports. Is there a way to consolidate multiple streamable MCP servers within a single ASP.NET application to reduce port usage?
Describe the solution you'd like
Could we add a property like Name, to [McpServerToolType] and use routing to differentiate which MCP service to connect to?
For example, carried by the following two classes with different Tools:
[McpServerToolType("Foo")]
class Foo {...}
[McpServerToolType("Bar")]
class Bar {...}
After calling app.MapMcp("mcp"), connecting to /mcp/Foo and /mcp/Bar can use different tools.
Duplicate of #1202 -- both are about hosting multiple MCP servers/endpoints in a single ASP.NET process (there via keyed services and multiple MapMcp calls, with maintainer discussion). Let's consolidate the discussion there.
Activity
Carl-Hugo commentedon Feb 23, 2026
Check #612 (comment) and let me know if that helps.
jeffhandley commentedon Jul 19, 2026
Duplicate of #1202 -- both are about hosting multiple MCP servers/endpoints in a single ASP.NET process (there via keyed services and multiple
MapMcpcalls, with maintainer discussion). Let's consolidate the discussion there.