Skip to content

Per User (Client) Tools Sample #724

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

PederHP
Copy link
Collaborator

@PederHP PederHP commented Aug 21, 2025

Had Copilot help create a sample of how to use ConfigureSessionOptions to make tools dynamic and client/user specific. See #714.

Copilot AI and others added 7 commits August 21, 2025 17:20
Co-authored-by: PederHP <127606677+PederHP@users.noreply.github.com>
Co-authored-by: PederHP <127606677+PederHP@users.noreply.github.com>
Co-authored-by: PederHP <127606677+PederHP@users.noreply.github.com>
…b-c4b4779d276e

Add ASP.NET Core MCP server sample showcasing per-user tool filtering
Copilot AI and others added 5 commits August 22, 2025 11:12
…s with route-based filtering

Co-authored-by: PederHP <127606677+PederHP@users.noreply.github.com>
Co-authored-by: PederHP <127606677+PederHP@users.noreply.github.com>
…a-1d92ba914d7b

Rename AspNetCoreMcpServerPerUserTools to AspNetCoreMcpPerSessionTools with route-based filtering
@PederHP
Copy link
Collaborator Author

PederHP commented Aug 22, 2025

I've updated the sample as per @halter73 's suggestion to use route as the criteria instead of a header - to avoid any confusion with the mechanisms provided by the upcoming authorization convenience. The sample should show how to use arbitrary criteria to modify the Tools collection in the ConfigureSessionOptions delegate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants