3D Texel vs TypeUI
A side-by-side look at the 3D Texel and TypeUI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
3
3D TexelDeveloper Tools · Local subprocess (stdio)Search/download 7,000+ PBR materials, HDRIs, decals, 3D assets; generate PBR materials and HDRIs.40FairAuth: not declaredVerdict: choose 3D Texel for developer tools work as a local process; 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?
3Choose 3D Texel when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
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 | 3 3D Texel | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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
3D Texel 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.
3D Texel
{
"mcpServers": {
"3d-texel": {
"command": "npx",
"args": [
"-y",
"github:Gatyh/3dtexel-mcp"
]
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
3D Texel is categorized under Developer Tools and uses a local stdio subprocess. TypeUI belongs to Developer Tools and uses a local stdio subprocess. Pick 3D Texel 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.
3D Texel 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 3d-texel and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 3D Texel has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. TypeUI has 47/100 (Fair) with 2 views, 0 installs and 2,021 GitHub stars.