Middleware tools list (different tool set based on user access)

Open
#759 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
api, backend

Research direction

The issue names the csharp-sdk API, middleware tool-list management, and the MCP connection flow, but no files or tests. Start by locating the API and middleware surfaces for registering tools, then define how a user's custom tool list is loaded and applied after access-token authentication. Done means different users can receive their own tool lists and MCP clients see those tools for the connection.

Written by the indexing model from the issue text.

Description

enhancement needs confirmation

Is your feature request related to a problem? Please describe.
Cannot implement dynamic list of tools per user. My MCP will support many users at the same time. Each user has a different tool set based on his current project.

Describe the solution you'd like
Incapsulated middleware tools list management. The list of tools could be loaded based on custom list of tools of a user from my custom database and applied into csharp-sdk api to expose it to MCP client as usual for the connection.

Additional context
The MCP server by default has no tools. Just after user got connected Unity Engine via SignalR using token, the list of tools dynamically got fetched from Unity Engine. Then user may use an MCP client to connect to the MCP server with the access token and start using the tools. User may even create brand new custom tool inside of the Unity Engine and the tool will be uploaded to the MCP server into private tools list.

Dominant language
C#
Stars
4.5k
Forks
814
Avg merge
9d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/csharp-sdk

All issues in modelcontextprotocol/csharp-sdk

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.