mcpField
T
Tengence GEO Agent

Tengence GEO Agent

Local
github.comBusiness & Marketing0Updated 2w ago
RepositoryVisit website

About Tengence GEO Agent

Tengence GEO Agent is a content planning, production, publishing, and monitoring engine for GEO/SEO teams. It offers CLI, MCP, and an agent runtime, with multi-site storage using SQLite by default and optional MySQL.

Key features

  1. 01Plan and ingest content
  2. 02Run article gate checks
  3. 03Publish to WordPress and submit to search
  4. 04Monitor GEO visibility
  5. 05Use CLI, MCP, or the built-in agent runtime
  6. 06Store multi-site data in SQLite or MySQL

Use cases

  1. 01Coordinate a GEO/SEO article pipeline
  2. 02Check articles against writing standards
  3. 03Publish site content and submit it to search
  4. 04Track GEO visibility across sites

MCP support

The MCP server exposes 29 tools for workspace, site, article, checks, publishing, planning, images, monitoring, database, search, diagnostics, utilities, and standards. It supports stdio and Streamable HTTP; HTTP uses Bearer authentication.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "com-tengence-geo-agent": {
      "command": "npx",
      "args": [
        "-y",
        "tengence-geo-agent"
      ]
    }
  }
}
Run commandnpx -y tengence-geo-agent

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmtengence-geo-agent0.1.3

Tools

72

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
pathstringYesabsolute directory path chosen by the user (e.g. ~/my-geo-workspace)
createbooleanNocreate the directory when missing (default false)

Details

From the project README

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.

  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)

PackageFormDescription
@tengence/geo-sdkLibrary15-domain capability layer, lazy-loaded, single require entry
@tengence/geo-cliCLI21 bins (ingest / gate / publish / images / submission / monitor / plan)
@tengence/geo-mcpMCP Server29 tools, stdio + HTTP dual transport, Bearer auth
@tengence/geo-agentAgent launcherRuns once DEEPSEEK_API_KEY is set (HARNESS=dsh|opencode|pi)

Quick start

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

Development & verification

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.