DotNetDevMCP

Contributing

Contributions of every size are welcome, and not only code.

flowchart LR
    Try[Run it on your solution] --> Report{Something off?}
    Report -- yes --> Issue[Bug report or Discussion]
    Report -- no --> Share[Share your numbers in Discussions]
    Issue --> Fix[Fix it yourself?]
    Fix --> PR[Pull request]
    Idea[Idea for a tool] --> Feature[Feature request]
    Docs[Something unclear here] --> Edit[Edit this wiki]

Ways to help

  1. Try it on your own solution and report what happened: large or multi-targeted solutions, and test suites on Microsoft.Testing.Platform, NUnit, MSTest or TUnit are the most valuable. Bug report, or post your numbers in Discussions.
  2. Pick a good first issue. Comment that you’re on it; the maintainer answers questions and reviews quickly.
  3. Edit this wiki. New MCP client setup, a clearer tutorial step, a troubleshooting entry.
  4. Propose a tool. Feature request: describe what your agent was trying to do and where it got stuck.

Building and testing

git clone https://github.com/csa7mdm/DotNetDevMCP.git
cd DotNetDevMCP
dotnet build -c Release
dotnet test -c Release

To try your build from an MCP client, point the client at src/DotNetDevMCP.Server/bin/Release/net10.0/dotnetdevmcp (.exe on Windows). The full guide, code style and pull request checklist are in CONTRIBUTING.md; the map of the code is on Architecture.

Changing how tests are selected or run? Re-run benchmarks/polly and put the before/after numbers in your pull request.

Everyone taking part follows the Code of Conduct. If the project saves you time, you can sponsor its development.