Liminality vs TypeUI
A side-by-side look at the Liminality and TypeUI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LiminalityDeveloper Tools · Remote HTTP/SSEReduces a request into grounded sub-questions, routes each to a real tool, returns a reusable route.44FairAuth: no auth requiredVerdict: choose Liminality for developer tools work over a hosted endpoint; 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?
LChoose Liminality when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
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 | L Liminality | |
|---|---|---|
| Category | Developer Tools | Architecture & Design |
| Quality signal | 44/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 2,152 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Liminality | View TypeUI |
Tools & capabilities
Liminality 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.
Liminality
{
"mcpServers": {
"liminality": {
"url": "https://physea.ai/mcp"
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Liminality is categorized under Developer Tools and uses a remote HTTP/SSE transport. TypeUI belongs to Architecture & Design and uses a local stdio subprocess. Pick Liminality for developer tools work and TypeUI for architecture & design.
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.
Liminality has no declared pricing — check the project's own site. Auth: no auth required. TypeUI has no declared pricing — check the project's own site. 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 liminality and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Liminality has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. TypeUI has 53/100 (Good) with 3 views, 0 installs and 2,152 GitHub stars.