elementor-mcp-agent 1.2.0 → 1.3.0

package/README.md

@@ -2,6 +2,8 @@
 
 [![npm version](https://img.shields.io/npm/v/elementor-mcp-agent.svg)](https://www.npmjs.com/package/elementor-mcp-agent)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
+[![Mogacode-ma/elementor-mcp-agent MCP server](https://glama.ai/mcp/servers/Mogacode-ma/elementor-mcp-agent/badges/score.svg)](https://glama.ai/mcp/servers/Mogacode-ma/elementor-mcp-agent)
+[![GitHub stars](https://img.shields.io/github/stars/Mogacode-ma/elementor-mcp-agent?style=social)](https://github.com/Mogacode-ma/elementor-mcp-agent/stargazers)
 
 > **Agency-grade MCP server for WordPress Elementor.** Multi-site management, safe Elementor edits with backup + auto-rollback + CSS flush, template export/import, global widget detection, screenshots, WP-CLI escape hatch.
 
@@ -9,6 +11,20 @@ Built for agencies running many client sites on Elementor / Elementor Pro who wa
 
 ---
 
+## How this was built
+
+elementor-mcp-agent was built end-to-end with Claude Code over ~48 hours. The process is intentionally open:
+
+- Architecture, code, tests, docs — all generated through Claude Code pair-programming sessions
+- The 7 bugs documented in [this post-mortem](https://dev.to/mogacode/7-bugs-i-caught-in-my-mcp-server-before-publishing-and-why-i-almost-shipped-a-data-corruption-5dfd) were caught in real E2E testing against a live WordPress + Elementor install, not after the fact
+- v1.2's post-write verification pattern was shipped 2 hours after a reader's comment ([Mads Hansen on Dev.to](https://dev.to/mogacode/7-bugs-i-caught-in-my-mcp-server-before-publishing-and-why-i-almost-shipped-a-data-corruption-5dfd/comments)) — the changelog credits the source
+
+This isn't vibe-coded software thrown over the wall. Every release ran through lint + typecheck + 27 unit tests + (for v1.0) full E2E against a real WordPress install before publishing. The MCP itself hardcodes guardrails that prevent the model from making destructive WP-CLI calls.
+
+I run a small WordPress agency and use this tool every day on client sites. If you're skeptical about agentic codegen for production infrastructure, the entire commit history is in the open — judge for yourself.
+
+---
+
 ## Why this exists
 
 There are 25+ WordPress MCP servers on GitHub today. None targets the **agency multi-site workflow** with:
@@ -217,6 +233,16 @@ v1.0.0 was tested in real conditions against a live WordPress install with Eleme
 
 ---
 
+## If this saved you time
+
+The fastest way to support the project is a [⭐ star on GitHub](https://github.com/Mogacode-ma/elementor-mcp-agent) — it helps other agencies running Elementor sites find this and tells me what to keep building.
+
+You can also:
+
+- Open an [issue](https://github.com/Mogacode-ma/elementor-mcp-agent/issues) for bugs, edge cases, or missing tools
+- Start a [discussion](https://github.com/Mogacode-ma/elementor-mcp-agent/discussions) for design or workflow questions
+- Share what you built with it — I'd love to hear
+
 ## License
 
 [MIT](./LICENSE) — © 2026 [MogaCode](https://mogacode.ma).

package/dist/server.js

@@ -3109,6 +3109,16 @@ ${msg}` }],
   const transport = new StdioServerTransport();
   await server.connect(transport);
   logger.info({ tools: tools.length }, `${pkg.name} v${pkg.version} ready`);
+  if (!process.env["SUPPRESS_BANNER"] && !process.env["CI"]) {
+    process.stderr.write(
+      `
+  \u25B8 ${pkg.name} v${pkg.version} \u2014 ${tools.length} tools ready.
+    if this helps you, a \u2B50 on github.com/Mogacode-ma/elementor-mcp-agent
+    is the best thanks. (set SUPPRESS_BANNER=1 to silence this)
+
+`
+    );
+  }
 }
 main().catch((e) => {
   logger.error(e.message);