Enables publishing content to WordPress sites, including article creation, gate checks, and publishing.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@tengence/geo-mcp Ingest hello-geo.md for site my-site and run quality checks"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GEO/SEO content production & publishing engine — full-pipeline automation from content planning → writing & ingest → gate checks → WordPress publishing → search submission → GEO monitoring. Three usage modes: CLI / MCP (AI clients) / built-in agent runtime loop. Default storage is a single-file multi-tenant SQLite (auto-initialized) with optional MySQL; designed for open source and multi-site use.
AI clients (any MCP-capable harness)
│ MCP (stdio or Streamable HTTP + Bearer)
▼
@tengence/geo-mcp 29 tools (workspace/site/article/check/publish/plan/image/monitor/db/search/diagnose/util/standards)
▼
@tengence/geo-cli 21 tengence-geo-* commands
▼
@tengence/geo-sdk 15-domain capability layer (site/db/wp/content/images/search/…)
▼
SQLite (auto-init) or MySQL (tengence_geo_*, isolated from prod tengence_omni_*)Package | Form | Description |
| Library | 15-domain capability layer, lazy-loaded, single require entry |
| CLI | 21 bins (ingest / gate / publish / images / submission / monitor / plan) |
| MCP Server | 29 tools, stdio + HTTP dual transport, Bearer auth |
| Agent launcher | Runs once |
Related MCP server: wp-cli-mcp
npm install
cp -R examples/site-template ~/tengence/sites/my-site
cd ~/tengence/sites/my-site && cp .env.example .env # fill in WP credentials / tokens
# Full CLI pipeline
export SITES_ROOT=~/tengence/sites
tengence-geo-article-ingest hello-geo ./hello-geo.md --site my-site --research ./hello-geo.research.md
tengence-geo-check-article hello-geo --site my-site
# MCP (any MCP-capable client; see docs/mcp-platforms.md)
node packages/geo-mcp/bin/geo-mcp.js # stdio
GEO_MCP_TOKEN=sk-xxx node packages/geo-mcp/bin/geo-mcp-http.js # HTTP
# Agent (runs once the API key is set)
export DEEPSEEK_API_KEY=sk-xxx
npx -y @tengence/geo-agentFull onboarding: docs/getting-started.md.
Architecture & design decisions (layering / multi-tenancy / init model / why MCP bridging)
Generic writing & GEO standards — shipped in @tengence/geo-sdk, consumed via the standards_list / standards_read / article_draft MCP tools (the requirements an article must satisfy)
npm run build # workspace consistency check
npm test # 138 tests (all green on SQLite)
npm run geo:sdk-smoke # SDK smoke testSecrets live only in SITES_ROOT/<site>/.env (gitignored); the repo ships only the .env.example template.
The production MySQL (tengence_omni_*) is never written by this repo; the new repo uniformly uses tengence_geo_*.
The MCP HTTP transport requires GEO_MCP_TOKEN (Bearer).
MIT
This server cannot be deployed
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Build, run, schedule, and publish AI video pipelines to YouTube and TikTok from any MCP client.
WordPress MCP server: generate SEO posts, AI images, autoblog & WooCommerce on your self-hosted site
Create and manage Lindo AI websites, pages, blogs, clients, and credits from any MCP client.
