CleanSlice vs Webflow MCP
A side-by-side look at the CleanSlice and Webflow MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CleanSlice for architecture & design work over a hosted endpoint; choose Webflow MCP 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 CleanSlice when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get-started, list-categories, search.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 52/100 · Good | 48/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 | WEBFLOW_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 18 | 141 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View CleanSlice | View Webflow MCP |
Tools & capabilities
CleanSlice tools 4
get-startedReturns the essential CleanSlice rules and conventions. **Call this first.list-categoriesLists all documentation categories available for search filteringsearchSearch docs by query, category, framework, phase, or tags. Returns **snippets** (keyword-in-context excerpts) and document pathsread-docRead the full content of a specific document by path. Use after `search` to get complete docs
Webflow MCP 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.
CleanSlice
{
"mcpServers": {
"cleanslice": {
"url": "https://docs.anthropic.com/en/docs/claude-code/mcp"
}
}
}
Webflow MCP
{
"mcpServers": {
"mcp-158": {
"command": "npx",
"args": [
"-y",
"webflow-mcp-server@latest"
],
"env": {
"WEBFLOW_TOKEN": "YOUR_WEBFLOW_TOKEN_HERE"
}
}
}
}
Frequently asked questions
CleanSlice is categorized under Architecture & Design and uses a remote HTTP/SSE transport. Webflow MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick CleanSlice for architecture & design work and Webflow MCP 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.
CleanSlice has no declared pricing — check the project's own site. Webflow MCP 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 cleanslice and mcp-158 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CleanSlice has a quality signal of 52/100 (Good) with 2 views, 0 installs and 18 GitHub stars. Webflow MCP has 48/100 (Fair) with 0 views, 0 installs and 141 GitHub stars.
