Stacktree vs Webflow — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Stacktree vs Webflow
In-depth architectural comparison of the Stacktree and Webflow MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Stacktree
Developer Tools · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Webflow
Developer Tools · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Stacktree if you need specialized Developer Tools tools running via a local process. Choose Webflow if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Stacktree when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Stacktree is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Webflow belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Stacktree when you need capabilities focused on developer tools and Webflow when you require tools for developer tools.
Restrict viewers to an email domain (one-time magic-link verify). Paid plans only.
set_agentation
Toggle the on-page Agentation feedback toolbar.
list_sites
List sites owned by this API key. Paged (`has_more` + cursor); filter with `client`.
delete_site
Hard delete a site.
link_wallet
Link your wallet so pages you publish are owned by your account.
list_feedback
Read viewer annotations left via the Agentation toolbar; unresolved first.
resolve_feedback
Mark a feedback item addressed, with an optional note.
+6 more tools listed on main page
Webflow Tools (5)
list_sites
List all Webflow sites accessible to the connected account. Returns each site's id, display name, short name, preview URL, last published time, and custom domains. Use to discover which Webflow sites are available before reading their CMS collections or site content.
get_site
Get metadata for a single Webflow site by its id, including display name, short name, preview URL, time zone, last published time, and custom domains. Use after list_sites to inspect a specific site before browsing its CMS collections and content.
list_collections
List the CMS collections defined on a Webflow site. Returns each collection's id, display name, slug, singular name, created time, and last updated time. Use to discover the CMS structure of a site before listing or reading collection items (the actual site content).
list_collection_items
List the items (records) in a Webflow CMS collection — the live site content such as blog posts, products, or team members. Returns paginated items with their id, draft/archived status, last published time, and fieldData (the CMS field values). Use to read the actual content stored in a Webflow col…
get_collection_item
Get a single item (record) from a Webflow CMS collection by its id. Returns the item's id, draft/archived status, last published time, and fieldData (the full CMS field values). Use after list_collection_items to read one piece of Webflow site content in detail.