Hatch vs TypeUI
A side-by-side look at the Hatch and TypeUI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hatch for developer tools work; choose TypeUI 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 TypeUI 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 | 33/100 · Emerging | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 |
Tools & capabilities
Hatch tools
No tool names declared yet. Check the project README from the listing page.
TypeUI 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.
Hatch
No confirmed install command for Hatch yet — follow the setup steps linked from its listing page rather than a guessed package name.
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Hatch is categorized under Developer Tools and uses an install path we have not confirmed yet. TypeUI belongs to Developer Tools and uses a local stdio subprocess. Pick Hatch for developer tools work and TypeUI 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. Hatch has no confirmed install command yet — follow its own setup instructions.
Hatch has no declared pricing — check the project's own site. TypeUI 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 hatch and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hatch has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. TypeUI has 47/100 (Fair) with 2 views, 0 installs and 2,021 GitHub stars.