Tengence GEO Agent

GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.

Manual Client & Custom JSON ConfigExpand JSON ▾

No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Tengence GEO Agent, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.

Documentation Overview

Tengence GEO Agent

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.

Code

  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_*)

Packages (monorepo)

Package	Form	Description
`@tengence/geo-sdk`	Library	15-domain capability layer, lazy-loaded, single require entry
`@tengence/geo-cli`	CLI	21 bins (ingest / gate / publish / images / submission / monitor / plan)
`@tengence/geo-mcp`	MCP Server	29 tools, stdio + HTTP dual transport, Bearer auth
`@tengence/geo-agent`	Agent launcher	Runs once `DEEPSEEK_API_KEY` is set (HARNESS=dsh\|opencode\|pi)

Quick start

Terminal

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-agent

Full onboarding: docs/getting-started.md.

Documentation

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)
Getting started
MCP integration (stdio / HTTP, any client)
Release & distribution (npm / Docker)

Development & verification

Terminal

npm run build          # workspace consistency check
npm test               # 138 tests (all green on SQLite)
npm run geo:sdk-smoke  # SDK smoke test

Security boundaries

Secrets 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).

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Tengence GEO Agent

We don't have a confirmed install command for Tengence GEO Agent yet, so we don't publish a generated one — a guessed package name would point at the wrong package or none at all. Follow the project's own README or setup instructions (https://github.com/tengence-team/tengence-geo-agent) for the current steps.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Tengence GEO Agent AllMCPs Directory Badge

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/tengence-geo-agent?style=directory)](https://allmcps.com/mcp/tengence-geo-agent)

HTML Embed

<a href="https://allmcps.com/mcp/tengence-geo-agent"><img src="https://allmcps.com/api/badge/tengence-geo-agent?style=directory" alt="Tengence GEO Agent on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Best SEO MCP servers →Alternatives to Tengence GEO Agent →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

Documentation Overview

Tengence GEO Agent

Code

  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_*)

Packages (monorepo)

Package	Form	Description
`@tengence/geo-sdk`	Library	15-domain capability layer, lazy-loaded, single require entry
`@tengence/geo-cli`	CLI	21 bins (ingest / gate / publish / images / submission / monitor / plan)
`@tengence/geo-mcp`	MCP Server	29 tools, stdio + HTTP dual transport, Bearer auth
`@tengence/geo-agent`	Agent launcher	Runs once `DEEPSEEK_API_KEY` is set (HARNESS=dsh\|opencode\|pi)

Quick start

Terminal

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-agent

Full onboarding: docs/getting-started.md.

Documentation

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)
Getting started
MCP integration (stdio / HTTP, any client)
Release & distribution (npm / Docker)

Development & verification

Terminal

npm run build          # workspace consistency check
npm test               # 138 tests (all green on SQLite)
npm run geo:sdk-smoke  # SDK smoke test

Security boundaries

Secrets 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).

License

MIT

Frequently Asked Questions about Tengence GEO Agent