{
"mcpServers": {
"mcp-server-dotnet-format": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP protocol for dotnet-format tool
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 325 days ago.
Will it work with my client?
Transport: stdio, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Server Dotnet Format and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) stdio server for formatting .NET projects and files using the dotnet format CLI. This project enables agent-based tools (such as GitHub Copilot) to invoke formatting commands programmatically, supporting both local and containerized workflows.

.editorconfig, StyleCop, and analyzer rules.global.json for the pinned version)dotnet build
You can run the server directly using the following configuration in your mcp.json:
"dotnet-format": {
"type": "stdio",
"command": "dotnet",
"args": [
"run",
"--project",
"/PATH/mcp-server-dotnet-format/src/McpServerDotnetFormat/McpServerDotnetFormat.csproj"
]
}
This will start the MCP stdio server, ready to accept formatting requests.
To build and publish the Docker image for multiple platforms:
dotnet publish /t:PublishContainer src/McpServerDotnetFormat/McpServerDotnetFormat.csproj
Example output:
Restore complete (0.2s)
McpServerDotnetFormat succeeded (6.6s) → src/McpServerDotnetFormat/bin/Release/net9.0/linux-arm64/publish/
McpServerDotnetFormat succeeded (7.2s) → src/McpServerDotnetFormat/bin/Release/net9.0/linux-x64/publish/
McpServerDotnetFormat succeeded (0.3s) → src/McpServerDotnetFormat/bin/Release/net9.0/publish/
Build succeeded in 9.1s
The resulting Docker image can be pushed to your registry (e.g., ghisguth/mcp-server-dotnet-format:latest).
You can run the server in a container using the following configuration:
"dotnet-format-docker": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghisguth/mcp-server-dotnet-format:latest"
],
"env": {}
}
This will start the MCP server inside a Docker container, exposing the same stdio interface.
Format an entire project:
dotnet format /path/to/YourProject.csproj
Format a specific file:
dotnet format /path/to/YourProject.csproj --include path/to/YourFile.cs
src/McpServerDotnetFormat/src/McpServerDotnetFormat.Tests/.editorconfig and StyleCop.See LICENSE for details.
For more details, see the source code and configuration files in the repository.