MCP Server Analyzer vs Dembrandt
A side-by-side look at the MCP Server Analyzer and Dembrandt MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Analyzer for developer tools work as a local process; choose Dembrandt for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server Analyzer when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ruff-check, ruff-format, ruff-check-ci.
Choose Dembrandt when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 3,806 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 5 | Not listed |
| Full listing | View MCP Server Analyzer | View Dembrandt |
Tools & capabilities
MCP Server Analyzer tools 5
ruff-checkLint Python code using RUFF to identify style violations and potential errors.ruff-formatFormat Python code using RUFF's fast formatter.ruff-check-ciRun RUFF linter with CI/CD-specific output formats.vulture-scanDetect dead/unused code using VULTURE.analyze-codeComprehensive analysis combining RUFF linting and VULTURE dead code detection.
Dembrandt tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server Analyzer
{
"mcpServers": {
"mcp-server-analyzer": {
"command": "uvx",
"args": [
"mcp-server-analyzer"
]
}
}
}
Dembrandt
{
"mcpServers": {
"dembrandt": {
"command": "npx",
"args": [
"-y",
"dembrandt"
]
}
}
}
Frequently asked questions
MCP Server Analyzer is categorized under Developer Tools and uses a local stdio subprocess. Dembrandt belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Server Analyzer for developer tools work and Dembrandt for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server Analyzer has no declared pricing — check the project's own site. Dembrandt has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-server-analyzer and dembrandt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Analyzer has a quality signal of 57/100 (Good) with 1 views, 0 installs and 11 GitHub stars. Dembrandt has 53/100 (Good) with 1 views, 0 installs and 3,806 GitHub stars.