Dev Tools
dobermanch4 estrelas
A growing collection of developer utility tools — available as a CLI, REST API, and MCP server, all powered by a single .NET library.
- Transporte
- stdio
- Status
- Local
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirA growing collection of developer utility tools — available as a CLI, REST API, and MCP server, all powered by a single .NET library.
Dev Tools is built around one idea: write a tool once, expose it everywhere. Every tool is a single C# class decorated with [ToolDefinition]. At build time, Roslyn source generators automatically produce a CLI command, an API endpoint, and an MCP tool definition - no boilerplate, no duplication.
The library covers everyday developer tasks: encoding and decoding (Base64, URL, case formats), cryptographic operations (hashing, encryption, JWT parsing), identifier generation (UUID v3-v7, ULID, tokens, passphrases), data formatting (JSON, XML), and more. Tools are independently installable and usable across all four frontends:
dotnet global tool, fully pipeableThe web UI is localized (English and Ukrainian), multi-arch Docker images are published on every release.
Try the live demo - no installation needed.
[ToolDefinition] attribute via Roslyn source generatorsecho "hello" | dev-tools base-encodinglinux/amd64 and linux/arm64, published on every release.cs file and UI component; the rest is wired up at build timeSee docs/tools.md for the full categorized reference with aliases and descriptions, and docs/tool-design.md for when an operation gets its own tool and when it is a mode of another.
Run locally with Docker:
docker run -p 8080:8080 ghcr.io/dobermanch/dev-tools-web
Open http://localhost:8080 in your browser.
Install as a dotnet global tool:
dotnet tool install --global Dev.Tools.Console
# Encode to Base64
dev-tools base-encoding "Hello, World!"
# → SGVsbG8sIFdvcmxkIQ==
# Pipe tools together
echo "Hello, World!" | dev-tools base-encoding | dev-tools base-encoding --transcoding Decode
# Format JSON (sort keys)
echo '{"b":2,"a":1}' | dev-tools json-formatter --sort-keys Ascending
# Get help
dev-tools --help
dev-tools hash --help
Or run without installing via Docker:
docker run --rm ghcr.io/dobermanch/dev-tools-console base-encoding "Hello, World!"
# → SGVsbG8sIFdvcmxkIQ==
# Pipe into the container
echo "Hello, World!" | docker run --rm -i ghcr.io/dobermanch/dev-tools-console base-encoding
Run as a Docker container:
docker run -p 8080:8080 ghcr.io/dobermanch/dev-tools-api
Call an endpoint:
# Encode to Base64
curl -X POST http://localhost:8080/tools/base-encoding \
-H "Content-Type: application/json" \
-d '{"text": "Hello, World!"}'
Interactive API documentation (Scalar UI) is available at http://localhost:8080/ui.
Once registered, your assistant can use any tool directly — e.g., "hash this text with SHA-256" or "generate 5 UUIDs".
Install the MCP server as a global tool and register it in your AI assistant configuration.
dotnet tool install --global Dev.Tools.Mcp
Add to AI agent MCP config
"dev-tools": {
"type": "stdio",
"command": "dev-tools-mcp"
}
Use Docker dev-tools-mcp image and register it in your AI assistant configuration.
Using stdio transport:
"dev-tools": {
"type": "stdio",
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "MCP_TRANSPORT=stdio", "ghcr.io/dobermanch/dev-tools-mcp"]
}
Using HTTP transport:
"dev-tools": {
"type": "http",
"command": "docker",
"args": ["run", "--rm", "-i", "ghcr.io/dobermanch/dev-tools-mcp"]
}
Embed the tools directly in your .NET application.
dotnet add package Dev.Tools
// Base64 encode
var encoded = await new BaseEncodingTool().RunAsync(
new BaseEncodingTool.Args("Hello, World!"),
CancellationToken.None);
Console.WriteLine(encoded.Text); // SGVsbG8sIFdvcmxkIQ==
The dev-tools image bundles the Web UI, REST API, and MCP server into a single container — useful for self-hosting or quick local demos.
docker run -p 80:80 -p 8080:8080 -p 8081:8081 ghcr.io/dobermanch/dev-tools
git clone https://github.com/dobermanch/dev-tools.git
cd dev-tools
dotnet restore
dotnet build
dotnet test
Run a specific test class:
dotnet test --filter "ClassName=BaseEncodingToolTests"
make web # Run the Blazor WASM UI locally
make web-watch # Run it with hot reload
make tool # Pack and install Dev.Tools.Console globally
make mcp # Pack and install Dev.Tools.Mcp globally
make nuget # Pack the Dev.Tools NuGet package
make docker # Build all Docker images locally
make clean # Remove build artifacts and Docker images
A growing collection of developer utility tools — available as a CLI, REST API, and MCP server, all powered by a single .NET library.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Dev Tools roda localmente via stdio.
Última verificação: 2026-10-28. A growing collection of developer utility tools — available as a CLI, REST API, and MCP server, all powered by a single .NET library.