A
licenseC
qualityD
maintenanceEnables AI agents to interact with Webflow APIs for managing sites, pages, components, CMS collections, and custom code.
32
1,483 npm
MIT
Webflow
Officialby webflow
Related Servers
Alternatives to Webflow
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.1,483 npmMIT
- AlicenseAqualityDmaintenanceEnables Claude to interact with Webflow's APIs for managing sites, retrieving information, and executing tasks using natural language.21,483 npm21MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover the sites on a connected account and read their CMS collections and live content items, such as blog posts, products, or team members. Runs either as a local stdio server or through the Pipeworx gateway, with plain-English questions routed to the right tool.340 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Vercel API to manage deployments, domains, projects, and environment variables.1,743 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides tools to interact with the Attio API, enabling management of resources in an Attio workspace.5-
TDQS
C2.8/5.0
Scored across 22 tools
Disambiguation4/5
Most tools have clearly distinct purposes, especially the data_*_tool group. However, there is potential confusion between component_builder, de_component_tool, and data_components_tool, as well as element_builder, element_snapshot_tool, and element_tool, though descriptions help differentiate.
Naming Consistency3/5
Tool names follow a general pattern but are inconsistent: some end with '_tool', some with '_builder', and a few have no suffix (e.g., get_designer_app_connection_info). The mix of verb_noun (ask_webflow_ai) and noun_tool (asset_tool) reduces consistency.
Tool Count4/5
22 tools is slightly above the typical 3-15 range for a single-purpose server, but Webflow's diverse functionality (design, CMS, enterprise, etc.) justifies a larger set. Still, some tools could be merged or pruned.
Completeness4/5
The tool surface covers major Webflow areas: assets, components, CMS, pages, scripts, sites, webhooks, design elements, styles, variables, and a guide. Minor gaps exist, such as form handling or e-commerce tools, but core workflows are well-supported.
Maintenance
ActivityInactive
ResponsivenessSlow