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
I have verified this would not be more appropriate as a feature request in a specific repository
I have searched existing discussions to avoid duplicates
Your Idea
It would be nice if I could somehow differentiate what MCP tools/prompts/resources are linked to what MCP-endpoint within a single host.
Imagine I host an ASP.NET Core host at my.domain.com.
From the same host, I can have two MCP endpoints running:
my.domain.com/public/sse => publicly available MCP server, public tools for the external world, customers my.domain.om/internal/sse => internal tools, in-house specific for employees (setup with auth, for example an API-key or similar).
app.Map("/public", p => p.UseMCP("public-mcp").AllowAnon();
app.Map("/internal", intern => intern.UseMCP("internal-mcp").RequireAuth();
Workarounds:
Create 2 independent hosts and run them on different ports in the same .NET app (not all hosting providers support multiple ports, for example Heroku only supports port 80).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Pre-submission Checklist
Your Idea
It would be nice if I could somehow differentiate what MCP tools/prompts/resources are linked to what MCP-endpoint within a single host.
Imagine I host an ASP.NET Core host at my.domain.com.
From the same host, I can have two MCP endpoints running:
my.domain.com/public/sse
=> publicly available MCP server, public tools for the external world, customersmy.domain.om/internal/sse
=> internal tools, in-house specific for employees (setup with auth, for example an API-key or similar).Workarounds:
Scope
Beta Was this translation helpful? Give feedback.
All reactions