Sharptools

Clone the repository to your local machine. SharpTools does not publish a pre-built binary so you must build it from source.

git clone https://github.com/kooshi/SharpToolsMCP.git
cd SharpToolsMCP

Build the entire SharpTools solution using the dotnet CLI. This compiles both the SSE server and the stdio server binaries.

dotnet build SharpTools.sln

Add SharpTools to your MCP client configuration using the stdio server binary. Replace /path/to/SharpTools.StdioServer with the actual path to the built binary in your repository's output directory.

{
  "mcpServers": {
    "SharpTools": {
      "type": "stdio",
      "command": "/path/to/SharpTools.StdioServer",
      "args": [
        "--log-directory", "/var/log/sharptools/",
        "--log-level", "Information",
        "--load-solution", "/path/to/YourSolution.sln"
      ]
    }
  }
}

For clients that support SSE transport, run the SSE server on a local port. This is useful for web-based MCP clients or when you want to share the server across multiple client connections.

cd SharpTools.SseServer
dotnet run -- --port 3005 --log-file ./logs/mcp-sse-server.log --log-level Debug --load-solution /path/to/YourSolution.sln

If you did not pass --load-solution at startup, use the LoadSolution tool from your MCP client to load a .sln file. Then use GetMembers, ViewDefinition, FindReferences, and other tools to explore your codebase.