modelcontextprotocol / modelcontextprotocol/csharp-sdk
Allow Integration with ASP.Net Core
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 814
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 4
Description
Is your feature request related to a problem? Please describe.
Many teams have already working APIs in place which are built using ASP.Net Core Controllers or Minimal APIs. It would be good to provide an easy way to leverage these APIs and expose them through the MCP.
Describe the solution you'd like
Since ASP.Net Core already has the API Explorer built in which allows looking at the metadata of endpoints, it could be as easy as providing a Middleware which would then generate the MCP description at the /resources/list endpoint.
Another Middleware could then listen at the /message endpoint and dispatch the calls to the appropriate Controller / Minimal Endpoint.
Describe alternatives you've considered
None
Additional context
The MCP spec has just introduces "normal" HTTP calls without SSE
https://github.com/modelcontextprotocol/specification/pull/206
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing ASP.NET Core API Explorer metadata and the MCP specification's normal HTTP calls. Define how middleware would generate MCP descriptions at /resources/list and dispatch calls from /message to Controllers or Minimal APIs. Done means an agreed integration design with implementation scope and coverage for both endpoint styles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100