Cms Mcp Hub

Created By
rahhuul2 months ago
439 MCP tools for managing CMS platforms with AI. Full REST API coverage for WordPress (143 tools), Shopify (147 tools), WooCommerce (95 tools), Framer (20 tools), Strapi (17 tools), and Ghost (17 tools). One command setup - works with Claude, Cursor, Windsurf, Copilot, and any MCP client.
Overview

CMS MCP Hub

439 MCP tools for managing CMS platforms with AI. No plugins required - connects directly via official APIs.

Packages

  • @cmsmcp/wordpress - 143 tools (full WordPress REST API v2)
  • @cmsmcp/shopify - 147 tools (full Shopify Admin REST API)
  • @cmsmcp/woocommerce - 95 tools (full WooCommerce REST API v3)
  • @cmsmcp/framer - 20 tools (Framer Server API)
  • @cmsmcp/strapi - 17 tools (Strapi REST API)
  • @cmsmcp/ghost - 17 tools (Ghost Admin API)

Features

  • Posts, pages, media, comments, users, plugins, themes, menus, blocks, templates
  • Products, orders, customers, inventory, collections, fulfillments, refunds
  • SEO (Yoast), custom fields (ACF), workflows, file uploads
  • 227 tests, TypeScript strict mode, published on npm

Install

  • npx @cmsmcp/wordpress
  • npx @cmsmcp/shopify
  • npx @cmsmcp/woocommerce

Server Config

{
  "mcpServers": {
    "wordpress": {
      "command": "npx",
      "args": [
        "-y",
        "@cmsmcp/wordpress"
      ],
      "env": {
        "WORDPRESS_URL": "https://yoursite.com",
        "WORDPRESS_USERNAME": "admin",
        "WORDPRESS_APP_PASSWORD": "your-app-password"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
rahhuul
Star
-
Language
-
License
-
Category

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