Harvis.dev vs Valet
A side-by-side look at the Harvis.dev and Valet MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
Harvis.devDeveloper ToolsDeploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.37FairAuth: not declaredVerdict: choose Harvis.dev for developer tools work; choose Valet for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
HChoose Harvis.dev when
- You need dedicated capabilities in the Developer Tools domain.
Choose Valet when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Harvis.dev | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
Tools & capabilities
Harvis.dev tools
No tool names declared yet. Check the project README from the listing page.
Valet 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.
Harvis.dev
No confirmed install command for Harvis.dev yet — follow the setup steps linked from its listing page rather than a guessed package name.
Valet
{
"mcpServers": {
"valet": {
"url": "https://api.valet.dev/mcp"
}
}
}
Frequently asked questions
Harvis.dev is categorized under Developer Tools and uses an install path we have not confirmed yet. Valet belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Harvis.dev for developer tools work and Valet 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. Harvis.dev has no confirmed install command yet — follow its own setup instructions.
Harvis.dev has no declared pricing — check the project's own site. Valet is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 harvis-dev and valet as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Harvis.dev has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Valet has 43/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.