Iconify vs Webflow — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Iconify vs Webflow
In-depth architectural comparison of the Iconify 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
Iconify
Developer Tools · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: No auth required
Webflow
Developer Tools · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Iconify if you need specialized Developer Tools tools running via a hosted cloud SSE transport. 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?
I
Choose Iconify when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Search for icons by keyword across all collections. Returns icon names in prefix:name format (e.g., "mdi:home"). Use get_icons to fetch SVG data for results.
get_icons
Get SVG code and dimensions for specific icons. Input icon names in prefix:name format (e.g., "mdi:home", "fa:star"). Returns SVG markup, width, and height.
list_collections
Browse available icon collections. Returns prefix, name, icon count, author, license, and category. Use the prefix with search_icons or get_icons.
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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Iconify is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Webflow belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Iconify when you need capabilities focused on developer tools and Webflow when you require tools for developer tools.
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.