Skip to main content
Glama
enesjakozh
kapilduraphe

Webflow MCP Server

by kapilduraphe
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Servidor MCP de Webflow

insignia de herrería

Este servidor MCP permite a Claude interactuar con las API de Webflow.

Prerrequisitos

  • Node.js (v16 o superior)

  • Aplicación de escritorio Claude

  • Cuenta de Webflow

  • Token de API de Webflow (token de sitio o token de acceso OAuth)

Related MCP server: Webflow

Instrucciones de configuración

1. Crear un token de API de Webflow

  • Inicie sesión en su cuenta de Webflow

  • Vaya a Configuración del sitio > Aplicaciones e integraciones

  • Generar un nuevo token de API

  • Copia el valor del token (no podrás volver a verlo)

Alternativamente, también puede generar un token de acceso OAuth.

2. Configuración inicial del proyecto

Instalar dependencias:

npm install

3. Configurar variables de entorno

Cree un archivo .env para el desarrollo local (no confirme este archivo):

WEBFLOW_API_TOKEN=your-api-token

4. Configurar Claude Desktop

Abra el archivo de configuración de Claude Desktop:

Para MacOS:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

Para Windows:

code %AppData%\Claude\claude_desktop_config.json

Agregar o actualizar la configuración:

{
    "mcpServers": {
        "webflow": {
            "command": "node",
            "args": [
                "/ABSOLUTE/PATH/TO/YOUR/build/index.js"
            ],
            "env": {
                "WEBFLOW_API_TOKEN": "your-api-token"
            }
        }
    }
}

Guarde el archivo y reinicie Claude Desktop.

Instalación mediante herrería

Para instalar Webflow MCP Server para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @kapilduraphe/webflow-mcp-server --client claude

Herramientas disponibles

El servidor actualmente proporciona las siguientes herramientas:

obtener_sitios

Recupera una lista de todos los sitios de Webflow accesibles para el usuario autenticado. Devuelve información detallada, incluyendo:

  • Nombre para mostrar del sitio y nombre corto

  • ID del sitio e ID del espacio de trabajo

  • Fechas de creación, última actualización y última publicación

  • URL de vista previa

  • Configuración de zona horaria

  • Configuración de dominios personalizados

  • Configuración de localización (configuraciones regionales primarias y secundarias)

  • Preferencias de recopilación de datos

obtener_sitio

Obtiene información detallada sobre un sitio Webflow específico por ID. Requiere un parámetro siteId y devuelve la misma información detallada que get_sites para un solo sitio.

Definiciones de tipos

interface WebflowApiError {
    status?: number;
    message: string;
    code?: string;
}

interface WebflowCustomDomain {
    id: string;
    url: string;
    lastPublished: string;
}

interface WebflowLocale {
    id: string;
    cmsLocaleId: string;
    enabled: boolean;
    displayName: string;
    redirect: boolean;
    subdirectory: string;
    tag: string;
}

interface WebflowSite {
    id: string;
    workspaceId: string;
    createdOn: string;
    displayName: string;
    shortName: string;
    lastPublished: string;
    lastUpdated: string;
    previewUrl: string;
    timeZone: string;
    parentFolderId?: string;
    customDomains: WebflowCustomDomain[];
    locales: {
        primary: WebflowLocale;
        secondary: WebflowLocale[];
    };
    dataCollectionEnabled: boolean;
    dataCollectionType: string;
}

Manejo de errores

El servidor gestiona varios escenarios de error:

Errores ambientales

  • Falta WEBFLOW_API_TOKEN

  • Token de API no válido

Solución de problemas

Problemas comunes

Herramientas que no aparecen en Claude

  • Consultar los registros de Claude Desktop

  • Verifique que WEBFLOW_API_TOKEN esté configurado correctamente

  • Asegúrese de que la ruta a index.js sea absoluta y correcta

Errores de autenticación

  • Verifique que su token API sea válido

  • Comprueba si el token tiene los permisos necesarios

  • Asegúrese de que el token no haya expirado

Visualización de registros

Para ver los registros del servidor:

Para MacOS/Linux:

tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

Para Windows:

Get-Content -Path "$env:AppData\Claude\Logs\mcp*.log" -Wait -Tail 20

Variables de entorno

Si recibe errores de variables de entorno, verifique:

  • WEBFLOW_API_TOKEN : Debe ser un token de API válido

Consideraciones de seguridad

  • Mantenga su token API seguro

  • No envíe credenciales al control de versiones

  • Utilice variables de entorno para datos confidenciales

  • Rotar regularmente los tokens API

  • Supervisar el uso de la API en Webflow

  • Utilice los permisos mínimos requeridos para el token API

Apoyo

Si encuentra algún problema:

  • Consulte la sección de solución de problemas más arriba

  • Revisar los registros de Claude Desktop

  • Examinar la salida de error del servidor

  • Consulte la documentación de la API de Webflow

Licencia

Licencia MIT: consulte el archivo LICENCIA para obtener más detalles.

Available Tools

2 tools
get_siteA

Retrieve detailed information about a specific Webflow site by ID, including workspace, creation date, display name, and publishing details

ParametersJSON Schema
NameRequiredDescriptionDefault
siteIdYesThe unique identifier of the Webflow site

TDQS

A3.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes the tool as a retrieval operation, which implies read-only behavior, but does not disclose other traits such as authentication requirements, rate limits, error handling, or response format. This leaves significant gaps for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that efficiently conveys the tool's purpose and key details without unnecessary words. It is front-loaded with the main action and resource, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple retrieval with one parameter), 100% schema coverage, but no output schema and no annotations, the description is adequate but incomplete. It covers the purpose and parameter semantics well, but lacks behavioral details like response format or error handling, which are important for a tool with no structured output information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'siteId' documented as 'The unique identifier of the Webflow site'. The description adds value by specifying that the tool retrieves information 'by ID', reinforcing the parameter's purpose, but does not provide additional syntax or format details beyond what the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Retrieve' and the resource 'detailed information about a specific Webflow site by ID', with specific details like workspace, creation date, display name, and publishing details. It distinguishes from the sibling tool 'get_sites' by specifying retrieval for a single site rather than multiple sites.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when detailed information for a specific site is needed, but does not explicitly state when to use this tool versus the sibling 'get_sites' or other alternatives. It provides clear context for retrieving site details by ID, but lacks explicit exclusions or comparisons.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_sitesB

Retrieve a list of all Webflow sites accessible to the authenticated user

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions authentication requirements, which is useful context. However, it lacks details on behavioral traits such as rate limits, pagination, error handling, or what 'accessible' entails (e.g., permissions, workspace scoping). For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that efficiently conveys the tool's purpose and key constraint (authentication). It is front-loaded with the main action and resource, with no wasted words or redundant information. Every part of the sentence earns its place by adding value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose and authentication context but lacks details on output format (e.g., structure of the list), error cases, or limitations. Without annotations or output schema, the description should ideally provide more behavioral context to be fully complete for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion about inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'retrieve' and resource 'list of all Webflow sites', making the purpose specific and understandable. It distinguishes from the sibling 'get_site' by indicating it returns a list rather than a single site, though it doesn't explicitly name the alternative. The description is not tautological and provides meaningful context about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by specifying 'accessible to the authenticated user', suggesting it should be used when needing all sites the user can access. However, it doesn't provide explicit guidance on when to use this vs. the sibling 'get_site' or other alternatives, nor does it mention any exclusions or prerequisites beyond authentication. The usage context is implied but not fully articulated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kapilduraphe/webflow-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server