Numen MCP Server — AI-Native CMS Protocol (MCP First Mover)

[Weegy]

Overview

Competitor: WordPress
Signal: WordPress shipped php-ai-client (provider-agnostic PHP AI SDK) — updated March 15, 2026. 252 GitHub stars. Meanwhile HN surfaced a WordPress MCP Server connecting Claude Desktop to WordPress via AI (July 2025). The WordPress AI Team was formally announced in May 2025. The pattern is clear: WordPress is building AI infrastructure piece by piece — PHP client → MCP server → Gutenberg AI blocks.

The gap: WordPress AI is bolt-on by design. Their php-ai-client is a standalone utility, not integrated into the content workflow. There is no concept of "AI agent" in WordPress — you call an AI helper, it returns text, you paste it. No pipeline. No memory. No persona.

What this means for Numen: WordPress's approach gives us a 12–18 month window before they have anything resembling a cohesive AI workflow. But here's the real opportunity: MCP (Model Context Protocol) as a first-class Numen integration. WordPress users are already connecting Claude Desktop to their CMS via community-built MCP servers. Numen should ship an official @numen/mcp-server that exposes the full AI pipeline as MCP tools — making Numen the CMS that any AI agent can orchestrate natively.

Proposed Feature: Numen MCP Server — AI-Native CMS Protocol

What it is: An official Model Context Protocol (MCP) server that exposes Numen's full content pipeline as MCP tools. Claude Desktop, Cursor, VS Code Copilot, and any MCP-compatible AI client can:

• Create and manage content briefs
• Run the AI content pipeline (Brief → Generate → Illustrate → SEO → Review)
• Query the content knowledge graph
• Publish, schedule, or draft content
• Manage media, taxonomies, and spaces
• Monitor pipeline status

Why it matters:

1. Zero-effort AI workflow: Developers and content teams can talk to their CMS from any AI tool — no custom integrations, no API wrangling
2. Competitive moat: No CMS has an official MCP server. First mover gets developer mindshare
3. Numen as AI infrastructure: Positions Numen not as "a CMS with AI" but as "AI-native content infrastructure"
4. WordPress defence: Their MCP server is community-built with ~3 stars. An official, deeply integrated Numen MCP server with pipeline support is incomparably better

Implementation scope:

• packages/mcp-server/ — standalone Node.js MCP server using @modelcontextprotocol/sdk
• MCP tools: create_brief, run_pipeline, get_content, publish_content, query_graph, list_spaces, manage_media
• SSE transport for real-time pipeline status streaming to AI clients
• Docker image + npx @numen/mcp-server one-liner launch
• Auth via Numen API tokens (Sanctum)

Competitor context: WordPress has a community MCP server (3 stars). Directus has nothing. Strapi has nothing. Payload has nothing. Sanity has nothing. First mover wins developer AI toolchain lock-in.

Priority: HIGH 🔴

MCP is becoming the universal protocol for AI-CMS integration. Numen's AI-first architecture makes this trivially natural — we're not retrofitting, we're exposing what we already have.