zed-mcp-server-webflow

Provides a Zed context server extension that integrates the Webflow MCP Server, configured via a Webflow token, so Zed’s Agent Panel can use Webflow-related actions/data through MCP.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ API Gateway mcp-server zed webflow context-server agent-panel rust

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

TLS and secure storage practices are not described in the provided material; scores assume typical HTTPS usage by upstream services but cannot verify. The extension requires a Webflow token; least-privilege scope and safe secret handling/rotation are not documented here. No security guidance (logs, redaction, storage) is provided in the snippet.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want Zed agents to call Webflow capabilities through an MCP server, and you can securely manage a Webflow token in Zed extension settings.

Avoid When

You cannot securely handle tokens or you need documented guarantees about reliability/error recovery semantics for agent retries.

Use Cases

• Enable Zed Agent Panel to interact with Webflow (via the underlying Webflow MCP server) using a configured Webflow access token.
• Assist agents in Webflow content/workflow tasks (e.g., retrieving or updating Webflow resources) from within Zed.

Not For

• General-purpose Webflow automation without using Zed or the MCP tooling.
• Use cases requiring fine-grained operational controls (rate limiting strategy, idempotency guarantees) that are not documented here.

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: webflow_token

OAuth: No Scopes: No

Auth method is implied by configuration: a Webflow token is provided in Zed extension settings as webflow_token. No further details on scope granularity, token type, or rotation are provided in the provided README.

Pricing

Free tier: No

Requires CC: No

No pricing information provided for the extension or the underlying Webflow/MCP services.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Only token-based configuration is shown; without the underlying MCP server documentation, agents may not know which tools are safe to retry or whether operations are idempotent.
⚠ Token handling/permissions are not described; agents may fail if the token lacks required Webflow permissions.
⚠ No rate-limit or quota behavior is documented here; agent callers may need to throttle conservatively.

Alternatives

Use Webflow’s native API directly (REST/GraphQL as applicable) from your own tooling. Use the Webflow MCP server standalone (outside of Zed) if you already run MCP-capable infrastructure. Build a custom Zed context server/MCP bridge around Webflow with your own auth, retry, and observability policies.

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for zed-mcp-server-webflow.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.