Automated-Webflow

Created By
ItsMeHarambea year ago
Connecting MCP Servers to a Webflow project
Overview

what is Automated-Webflow?

Automated-Webflow is a project designed to connect MCP (Multi-Channel Publishing) servers to a Webflow project, enabling seamless integration and automation of web content management.

how to use Automated-Webflow?

To use Automated-Webflow, clone the repository from GitHub, configure your MCP server settings, and follow the setup instructions provided in the documentation to connect it to your Webflow project.

key features of Automated-Webflow?

  • Integration of MCP servers with Webflow for automated content updates.
  • Simplified management of web content through automation.
  • Open-source project with community support.

use cases of Automated-Webflow?

  1. Automating the publishing of content from MCP servers to Webflow.
  2. Streamlining the workflow for web developers managing multiple content sources.
  3. Enhancing the efficiency of web content updates and management.

FAQ from Automated-Webflow?

  • What is the purpose of Automated-Webflow?

Automated-Webflow connects MCP servers to Webflow, allowing for automated content management and updates.

  • Is Automated-Webflow free to use?

Yes! Automated-Webflow is an open-source project and is free to use.

  • How can I contribute to Automated-Webflow?

You can contribute by submitting issues, feature requests, or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ItsMeHarambe
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago