Webflow MCP vs TypeUI
A side-by-side look at the Webflow MCP 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 Webflow MCP for architecture & design work as a local process; 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 Webflow MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WEBFLOW_TOKEN. - You want tools like
webflow_guide_tool, ask_webflow_ai, collections_list.
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 | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 67/100 · Great | 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 | WEBFLOW_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 140 | 2,134 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 43 | Not listed |
| Full listing | View Webflow MCP | View TypeUI |
Tools & capabilities
Webflow MCP tools 43
webflow_guide_toolProvides essential guidelines and best practices for effectively using the Webflow tools. Call this tool to understand recommended workflows and important considerations before performing actions. ALWAYS CALL THIS TOOL FIRST BEFORE CALLING ANY OTHER TOOLS. ALWAYS CALL THIS TOOL FIRST BEFORE CALLING ANY OTHER TOOLS.ask_webflow_aiAsk Webflow AI about anything related to Webflow API.collections_listList all CMS collections in a site. Returns collection metadata including IDs, names, and schemas.collections_getGet detailed information about a specific CMS collection including its schema and field definitions.collections_createCreate a new CMS collection in a site with specified name and schema.collection_fields_create_staticCreate a new static field in a CMS collection (e.g., text, number, date, etc.).collection_fields_create_optionCreate a new option field in a CMS collection with predefined choices.collection_fields_create_referenceCreate a new reference field in a CMS collection that links to items in another collection.collection_fields_updateUpdate properties of an existing field in a CMS collection.collections_items_create_item_liveCreate and publish new items in a CMS collection directly to the live site.collections_items_update_items_liveUpdate and publish existing items in a CMS collection directly to the live site.collections_items_list_itemsList items in a CMS collection with optional filtering and sorting.- +31 more on 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.
Webflow MCP
{
"mcpServers": {
"mcp-158": {
"command": "npx",
"args": [
"-y",
"webflow-mcp-server@latest"
],
"env": {
"WEBFLOW_TOKEN": "YOUR_WEBFLOW_TOKEN_HERE"
}
}
}
}
TypeUI
{
"mcpServers": {
"typeui": {
"command": "npx",
"args": [
"-y",
"typeui.sh"
]
}
}
}
Frequently asked questions
Webflow MCP is categorized under Architecture & Design and uses a local stdio subprocess. TypeUI belongs to Architecture & Design and uses a local stdio subprocess. Pick Webflow MCP 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.
Webflow MCP 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 mcp-158 and typeui as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Webflow MCP has a quality signal of 67/100 (Great) with 1 views, 0 installs and 140 GitHub stars. TypeUI has 47/100 (Fair) with 2 views, 0 installs and 2,134 GitHub stars.