Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/webflow/mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/webflow/mcp-server/mcp)<a href="https://agentmods.dev/mcp/webflow/mcp-server/mcp"><img src="https://agentmods.dev/badge/mcp/webflow/mcp-server/mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/webflow/mcp-server/mcp"><img src="https://agentmods.dev/badge/mcp/webflow/mcp-server/mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mcp": {
"url": "https://mcp.webflow.com/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A ea3311206aaa
mcp is an MCP server published in the GitHub repository webflow/mcp-server (141 stars, last pushed 10d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
zenith
Author, validate, edit, and render deterministic .zen design docs to PNG/PDF. Runs locally from the @zenitheditor/zenith-mcp npm package.
figma-edit-mcp
Programmatically read, create, and modify Figma designs via MCP. Runs locally from the figma-edit-mcp npm package.
TalkToFigma
MCP server "TalkToFigma" as configured in neozhehan/figma-edit-mcp. Runs locally from the vscode-talk-to-figma-mcp npm package.
vynix-mcp
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis. Runs locally from the @usevynix/mcp-server npm package. Needs 2 environment variables to run.
a1-gallery
Search a curated gallery of real website designs by style, font, colour, section and technology. Remote server at www.a1.gallery.
standby-design-mcp
Generate design systems: OKLCH color palettes, fluid type scales, spacing, shape and icon tokens. Runs locally from the standby-design-mcp npm package.