Skip to main content
Glama
enesjakozh
kapilduraphe

Webflow MCP Server

by kapilduraphe
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Webflow MCP サーバー

鍛冶屋のバッジ

この MCP サーバーにより、Claude は Webflow の API と対話できるようになります。

前提条件

  • Node.js (v16 以上)

  • クロードデスクトップアプリ

  • Webflowアカウント

  • Webflow APIトークン（サイトトークンまたはOAuthアクセストークン）

Related MCP server: Webflow

セットアップ手順

1. Webflow APIトークンを作成する

  • Webflowアカウントにログイン

  • サイト設定 > アプリと統合に移動します

  • 新しいAPIトークンを生成する

  • トークンの値をコピーします（再度表示することはできません）

あるいは、OAuth アクセス トークンを生成することもできます。

2. プロジェクトの初期設定

依存関係をインストールします:

npm install

3. 環境変数を設定する

ローカル開発用の.envファイルを作成します (このファイルはコミットしないでください)。

WEBFLOW_API_TOKEN=your-api-token

4. Claudeデスクトップを設定する

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 Server を自動的にインストールするには:

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 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 ライセンス - 詳細については LICENSE ファイルを参照してください。

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedget_site
    • First observedget_sites
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