Skip to content

Archive webflow/mcp-server — README notice → public Beta MCP + community#132

Open
bertenator wants to merge 3 commits into
mainfrom
albertchang/archive-mcp-server-notice
Open

Archive webflow/mcp-server — README notice → public Beta MCP + community#132
bertenator wants to merge 3 commits into
mainfrom
albertchang/archive-mcp-server-notice

Conversation

@bertenator

@bertenator bertenator commented Jun 8, 2026

Copy link
Copy Markdown
Member

Summary

This repo (webflow-mcp-server) is the open-source, self-hosted Webflow MCP server — the package you run locally. Webflow now runs a hosted, remote MCP server that customers connect to directly, and that hosted server is how the Webflow MCP is used today. We're consolidating onto the hosted server, so this OSS repo is being archived.

This PR adds a README notice that makes that distinction explicit and redirects visitors to the hosted MCP, docs/changelog, and the community.

⛔ Messaging — pending sign-off (do not merge yet)

Per #team-devrel feedback, the wording must not imply the Webflow MCP is deprecated:

  • Reframed "no longer maintained / issues disabled" → the OSS/self-hosted distribution is being retired; the hosted server is how customers use the MCP; this is a distribution change, not a deprecation.
  • Labeled as OSS / self-hosted, not generically "Webflow MCP".
  • Verbose + explicit.

Needs sign-off from DevRel + dev marketing before merge (and a possible Dev Newsletter note).

Before merging

  • Confirm community.webflow.com is live — it's a placeholder (TODO comment beside it in the README).

After merging

  • Archive the repo: gh repo archive webflow/mcp-server (also disables issues).

🤖 Generated with Claude Code

webflow/mcp-server is being archived. Add a prominent README notice that
redirects visitors to the actively-developed public Beta MCP
(developers.webflow.com/mcp/installing/beta), the docs + changelog, and the
community for engagement and bug reporting (issues are being disabled).

The community link (community.webflow.com) is a placeholder pending confirmation
that it is live — flagged with a TODO comment in the README.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@bertenator bertenator self-assigned this Jun 8, 2026
@bertenator bertenator marked this pull request as ready for review June 8, 2026 18:09
@bertenator bertenator requested a review from a team as a code owner June 8, 2026 18:09
@bertenator bertenator requested review from markconigliaro1 and viratatwebflow and removed request for a team and markconigliaro1 June 8, 2026 18:09
bertenator and others added 2 commits June 8, 2026 22:28
…e MCP

Per #team-devrel feedback on the messaging:
- Avoid "no longer maintained / issues disabled" framing that reads as Webflow
  abandoning the MCP.
- Clarify this repo is the open-source, SELF-HOSTED MCP server; the hosted/remote
  server is how customers use the Webflow MCP today.
- Frame archiving as a distribution change (consolidating onto the hosted server),
  not a deprecation. Label as OSS, not generically "Webflow MCP". Be verbose.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ix repo name

- The "self-hosted / run locally only" framing was inaccurate: this repo's README
  documents connecting to the hosted server (https://mcp.webflow.com/sse) as the
  primary path. Reframe around OSS repo vs hosted service, not self-hosted vs hosted.
- Use the GitHub repo name `webflow/mcp-server` instead of the npm package name.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant