modelcontextprotocol / modelcontextprotocol/csharp-sdk
AspNetCore TestHost client transport
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.
From what I can see, I don't think there is currently a way to create an MCP client against an AspNetCore TestHost
Describe the solution you'd like
Adding means to create an MCP client against a TestHost
Describe alternatives you've considered
Re-configure the server to use a different transport for integration testing purposes as done in ClientServerTestBase. That works, but is arguably a little less elegant than out of the box support for TestHost
Additional context
Add any other context or screenshots about the feature request here.
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 reading ClientServerTestBase and the existing TestHost-related integration setup to understand how transport is currently reconfigured for tests. Trace the client creation path and identify what support is needed for an AspNetCore TestHost. Done means an MCP client can connect to a TestHost directly, with integration coverage demonstrating the supported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100