Intangible vs TypeUI
A side-by-side look at the Intangible and TypeUI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
I
IntangibleArchitecture & Design · Remote HTTP/SSEBuild 3D scenes, place cameras and render shots. Previs, storyboards, set design, product and CAD.42FairAuth: not declaredVerdict: choose Intangible for architecture & design 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?
IChoose Intangible when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
Choose TypeUI when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | I Intangible | |
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 42/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 |
| GitHub stars | — | 2,134 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Intangible | View TypeUI |
Tools & capabilities
Intangible 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.
Intangible
{
"mcpServers": {
"intangible": {
"url": "https://www.intangible.ai/mcp"
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Intangible is categorized under Architecture & Design and uses a remote HTTP/SSE transport. TypeUI belongs to Architecture & Design and uses a local stdio subprocess. Pick Intangible for architecture & design 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.
Intangible 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 intangible and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Intangible has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. TypeUI has 47/100 (Fair) with 2 views, 0 installs and 2,134 GitHub stars.