EVMole vs Extensiondev MCP
A side-by-side look at the EVMole and Extensiondev MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose EVMole for developer tools work as a local process; choose Extensiondev MCP 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 EVMole when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Extensiondev MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 473 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View EVMole | View Extensiondev MCP |
Tools & capabilities
EVMole tools
No tool names declared yet. Check the project README from the listing page.
Extensiondev MCP 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.
EVMole
{
"mcpServers": {
"evmole": {
"command": "npx",
"args": [
"-y",
"evmole"
]
}
}
}
Extensiondev MCP
{
"mcpServers": {
"mcp-291": {
"command": "npx",
"args": [
"@extension.dev/mcp"
]
}
}
}
Frequently asked questions
EVMole is categorized under Developer Tools and uses a local stdio subprocess. Extensiondev MCP belongs to Developer Tools and uses a local stdio subprocess. Pick EVMole for developer tools work and Extensiondev MCP 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.
EVMole has no declared pricing — check the project's own site. Extensiondev MCP is listed as free. Auth: no auth required. 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 evmole and mcp-291 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, EVMole has a quality signal of 51/100 (Good) with 0 views, 0 installs and 473 GitHub stars. Extensiondev MCP has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.