Tengence GEO Agent

com.tengencev0.1.3Updated Oct 7, 2026

GEO/SEO content engine: planning, writing, gate checks, WordPress publishing, GEO monitoring.

VerifiedSTDIODesktop onlyBusiness & CommerceWeb Search & ScrapingProductivity & Workflow

Overview

AI-generated overview

Lets an assistant plan, write, gate-check, publish, and monitor GEO/SEO content for WordPress sites through a 29-tool MCP server.

What it does
A GEO/SEO content production and publishing engine exposed as an MCP server with 29 tools grouped around workspace, site, article, check, publish, plan, image, monitor, database, search, diagnose, utility, and standards. It covers the pipeline from content planning and writing/ingest through gate checks, WordPress publishing, search submission, and GEO monitoring. It also ships a CLI with 21 commands and an SDK capability layer, and can run as a built-in agent loop.
When to use it
Use it when an assistant should help run an end-to-end SEO/GEO content workflow for one or more WordPress sites: drafting and ingesting articles, enforcing writing standards, checking articles before publishing, pushing them live, and tracking search visibility. It suits multi-site or multi-tenant setups that want a single local content engine.
Requirements
Runs locally over stdio via the npm package tengence-geo-agent (Node.js). Sites live under a SITES_ROOT directory, each with its own .env holding WordPress credentials and tokens. The optional HTTP transport needs GEO_MCP_TOKEN as a Bearer token, and the agent launcher needs DEEPSEEK_API_KEY. Storage defaults to an auto-initialized SQLite file, with optional MySQL.
Before you install
It publishes to WordPress and submits to search engines, so it writes to live sites and third-party services. WordPress credentials and tokens sit in each site's .env, and the HTTP transport is protected by GEO_MCP_TOKEN; treat these as secrets. The agent launcher sends content to the DeepSeek API using DEEPSEEK_API_KEY. The README states the production MySQL tengence_omni_* is never written and the repo uses tengence_geo_* instead.

Installation

In SourceWeft

  1. Open Tengence GEO Agent in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

bash
npm installcp -R examples/site-template ~/tengence/sites/my-sitecd ~/tengence/sites/my-site && cp .env.example .env   # fill in WP credentials / tokens
# Full CLI pipelineexport SITES_ROOT=~/tengence/sitestengence-geo-article-ingest hello-geo ./hello-geo.md --site my-site --research ./hello-geo.research.mdtengence-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                          # stdioGEO_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-xxxnpx -y @tengence/geo-agent

Full onboarding: docs/getting-started.md.

Documentation

Development & verification

bash
npm run build          # workspace consistency checknpm 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

Source: README.md at commit cf1bfc3

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.3LatestOct 7, 2026