Skip to main content
Glama
enesjakozh
kapilduraphe

Webflow MCP Server

by kapilduraphe
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

웹플로우 MCP 서버

대장간 배지

이 MCP 서버를 통해 Claude는 Webflow의 API와 상호 작용할 수 있습니다.

필수 조건

  • Node.js(v16 이상)

  • 클로드 데스크톱 앱

  • 웹플로우 계정

  • Webflow API 토큰(사이트 토큰 또는 OAuth 액세스 토큰)

Related MCP server: Webflow

설치 지침

1. Webflow API 토큰 생성

  • Webflow 계정에 로그인하세요

  • 사이트 설정 > 앱 및 통합으로 이동합니다.

  • 새로운 API 토큰 생성

  • 토큰 값을 복사하세요(다시는 볼 수 없습니다)

혹은 OAuth 액세스 토큰을 생성할 수도 있습니다.

2. 초기 프로젝트 설정

종속성 설치:

지엑스피1

3. 환경 변수 구성

로컬 개발을 위해 .env 파일을 만듭니다(이 파일을 커밋하지 마세요):

WEBFLOW_API_TOKEN=your-api-token

4. Claude Desktop 구성

Claude Desktop 구성 파일을 엽니다.

MacOS의 경우:

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

Windows의 경우:

code %AppData%\Claude\claude_desktop_config.json

구성을 추가하거나 업데이트합니다.

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

파일을 저장하고 Claude Desktop을 다시 시작하세요.

Smithery를 통해 설치

Smithery를 통해 Claude Desktop에 Webflow MCP 서버를 자동으로 설치하려면:

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

사용 가능한 도구

현재 서버는 다음과 같은 도구를 제공합니다.

get_sites

인증된 사용자가 액세스할 수 있는 모든 Webflow 사이트 목록을 검색합니다. 다음을 포함한 자세한 정보를 반환합니다.

  • 사이트 표시 이름 및 약어

  • 사이트 ID 및 작업 공간 ID

  • 생성, 최종 업데이트 및 최종 게시 날짜

  • 미리보기 URL

  • 시간대 설정

  • 사용자 정의 도메인 구성

  • 지역화 설정(기본 및 보조 로케일)

  • 데이터 수집 기본 설정

get_site

ID를 기준으로 특정 Webflow 사이트에 대한 자세한 정보를 검색합니다. siteId 매개변수가 필요하며, 단일 사이트에 대한 get_sites와 동일한 자세한 정보를 반환합니다.

유형 정의

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;
}

오류 처리

서버는 다양한 오류 시나리오를 처리합니다.

환경 오류

  • WEBFLOW_API_TOKEN이 없습니다

  • 잘못된 API 토큰

문제 해결

일반적인 문제

Claude에 도구가 나타나지 않음

  • Claude Desktop 로그 확인

  • WEBFLOW_API_TOKEN이 올바르게 설정되었는지 확인하세요.

  • index.js 경로가 절대적이고 올바른지 확인하세요.

인증 오류

  • API 토큰이 유효한지 확인하세요

  • 토큰에 필요한 권한이 있는지 확인하세요

  • 토큰이 만료되지 않았는지 확인하세요

로그 보기

서버 로그를 보려면:

MacOS/Linux의 경우:

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

Windows의 경우:

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

환경 변수

환경 변수 오류가 발생하는 경우 다음을 확인하세요.

  • WEBFLOW_API_TOKEN : 유효한 API 토큰이어야 합니다.

보안 고려 사항

  • API 토큰을 안전하게 유지하세요

  • 버전 제어에 자격 증명을 커밋하지 마세요

  • 민감한 데이터에 환경 변수를 사용하세요

  • API 토큰을 정기적으로 회전합니다

  • Webflow에서 API 사용 모니터링

  • API 토큰에 필요한 최소 권한 사용

지원하다

문제가 발생하면:

  • 위의 문제 해결 섹션을 확인하세요

  • Claude Desktop 로그 검토

  • 서버의 오류 출력을 검사합니다.

  • Webflow의 API 문서를 확인하세요

특허

MIT 라이센스 - 자세한 내용은 라이센스 파일을 참조하세요.

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