Axiom vs TypeUI
A side-by-side look at the Axiom 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 Axiom for developer tools work; choose TypeUI for architecture & design 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 Architecture & Design 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 | A Axiom | |
|---|---|---|
| Category | Developer Tools | Architecture & Design |
| Quality signal | 12/100 · Emerging | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 2,153 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Axiom | View TypeUI |
Tools & capabilities
Axiom 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.
Axiom
No confirmed install command for Axiom 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"
]
}
}
}