Elementeer MCP

Elementeer MCP

[!NOTE]Public mirror. The canonical repository is hosted on our self-hosted git.This GitHub copy is a read-only mirror kept in sync for visibility andinstallation. Bug reports are welcome via Issues; pull requests are appliedupstream and synced back here.

The Model Context Protocol server connecting AI agents to Elementeer-powered WordPress sites.

A Node.js MCP server with 128+ tools in the Free tier, 250+ tools total, 65 fine-grained capabilities, and L0–L3 governance for safe AI-agent operation. Handles template composition, site assessment, brand setup, creator workflows, theme building, navigation, media, SEO, performance, translation, accessibility, LMS, charity, booking, e-commerce, and addon ecosystem management — all through a single protocol surface.

Companion plugin: elementeer/elementeer — exposes /wp-json/elementeer/v1/ on your WordPress site.

Quick Start

1. Install the WordPress plugin

Download from elementeer/elementeer → Upload → Activate → Settings → Elementeer MCP → Generate Key.

2. Install the MCP server

npm install -g @elementeer/mcp
elementeer-mcp init   # creates ~/.elementeer/config.json

3. Configure your sites

Edit ~/.elementeer/config.json:

{
  "sites": [
    {
      "id": "my-site",
      "name": "My WordPress Site",
      "url": "https://yoursite.com",
      "apiKey": "ek_your_key_here",
      "default": true
    }
  ]
}

4. Add to your MCP client

{
  "mcpServers": {
    "elementeer": {
      "command": "elementeer-mcp"
    }
  }
}

From Capacium

cap install elementeer-mcp

Tools

Template Library

Site Intelligence

Brand & Design

Content

Navigation

Media

SEO

Governance

Integration Families

All adapters auto-detect their respective plugins. Tools for WooCommerce, Voxel, Amelia booking, LearnDash/Tutor LMS, GiveWP/Charitable, accessibility (Ally), translation (WPML/Polylang), and addon ecosystem analytics — each with domain-appropriate read/write operations, widget inventories, usage tracking, and overlap detection.

Governance Levels

Elementeer enforces a four-tier governance model for safe AI operation:

L2 tools call queue_change automatically. L3 tools require consent: true in the request. This gives AI agents the freedom to propose meaningful changes while keeping site owners in control.

Permission Architecture

Layer 1 — API Key Capabilities. Each key carries an explicit list of domain capabilities. A read-only key returns elementeer_insufficient_scope — not elementeer_invalid_key — on any write attempt, so the agent can guide the user precisely.

Layer 2 — Governance Settings. Site administrators configure allowed_capabilities in the WordPress admin. Even if a key has a capability, if governance blocks it, the server returns elementeer_governance_blocked. Site owners lock down entire domains without revoking keys.

The MCP server maps these error codes to typed ElementeerErrorCode values so AI clients receive actionable error information.

Product Tiers

Architecture

elementeer-mcp/
├── mcp-server/                 # TypeScript MCP server
│   ├── src/
│   │   ├── index.ts           # Server entry point & tool registration
│   │   ├── client.ts          # Axios HTTP client for WordPress API
│   │   ├── config.ts          # ~/.elementeer/config.json management
│   │   └── tools/             # 128+ tool implementations
│   ├── dist/                  # Compiled output (npm entry: dist/index.js)
│   └── package.json           # @elementeer/mcp v2.1.4
│
├── shared/                    # Shared TypeScript types & validation
│   ├── src/
│   └── package.json           # @elementeer/shared
│
├── mirror/                    # Free mirror staging & sync scripts
│
├── capability.yaml            # MCP capability manifest (65 capabilities)
├── TIERS.md                   # Tier comparison & pricing logic
├── CHANGELOG.md
├── ROADMAP.md
└── packages/                  # npm workspace root

Tech stack: TypeScript 5.4+ (strict mode), Zod validation, Axios HTTP client, Vitest test runner, npm workspaces.

Agent Setup

Elementeer MCP works with any MCP-compatible client.

Claude Desktop

{
  "mcpServers": {
    "elementeer": { "command": "elementeer-mcp" }
  }
}

Cursor

{
  "mcpServers": {
    "elementeer": { "command": "elementeer-mcp" }
  }
}

OpenCode

opencode mcp add elementeer -- elementeer-mcp

Antigravity / Codex

As configured in their respective mcpServers settings — use elementeer-mcp as the command and add site configuration in ~/.elementeer/config.json.

Capacium

cap install elementeer-mcp

Development

npm install
npm run build
npm run test --workspace=mcp-server
npm run test:coverage --workspace=mcp-server
npm run test:watch --workspace=mcp-server
npm run test --workspace=shared

Contributing

1. Fork and clone
2. Create a branch: git checkout -b feat/your-feature
3. Make changes with tests
4. Run npm test
5. Open a pull request using the template

Links

• Documentation: docs.elementeer.xyz
• WordPress Plugin: github.com/elementeer/elementeer
• Conversion Bridge: github.com/elementeer/elementeer-bridge
• Pro Addon: github.com/elementeer/elementeer-pro (private)

License

MCP Server: Apache-2.0

Bundled Plugin (Free): GPL-2.0-or-later — see elementeer/elementeer.

Pro Addon: Proprietary — see elementeer/elementeer-pro (private).