Webflow MCP Server
Related Servers
Alternatives to Webflow MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with Webflow's APIs, allowing access to site information, collections, and other Webflow resources.2,274 npmMIT
- AlicenseCqualityDmaintenanceEnables AI agents to interact with Webflow APIs for managing sites, pages, components, CMS collections, and custom code.322,274 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with the Webflow Data API and Designer, so users can query and manage sites, CMS collections and blog content, update pages, and build responsive page elements through natural language. Supports both remote OAuth-based and local API-token installations in clients such as Cursor and Claude Desktop.402 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with the Webflow Data API to manage sites, CMS content, and Designer app connections through natural language.402 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with Webflow's Data API and Designer, supporting site content management, design updates, and OAuth or API-token authentication through natural language.402 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with Webflow Data APIs and the Webflow Designer, supporting site content management, blog analysis, internal linking, and responsive design updates via natural language.402 npmMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get_site retrieves detailed information for a specific site by ID, while get_sites lists all accessible sites. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on whether it needs a single site's details or a list of sites.
Both tools follow a consistent verb_noun naming pattern (get_site and get_sites), using the same verb 'get' and singular/plural forms of 'site' to indicate scope. This predictable naming makes the tool set easy to understand and use.
With only 2 tools, the server feels severely under-scoped for a Webflow integration, which typically involves managing sites, collections, items, and other resources. This limited set will likely cause agents to hit dead ends when trying to perform common operations like creating or updating sites.
The tool set is incomplete for Webflow's domain, covering only read operations (get) for sites. It lacks essential CRUD operations such as create_site, update_site, delete_site, and tools for managing collections, items, or other Webflow resources, creating significant gaps that will hinder agent workflows.