Tengence GEO Agent

com.tengencev0.1.2Updated Oct 2, 2026

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

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & CommerceProductivity & Workflow

Overview

AI-generated overview

Lets an assistant run a GEO/SEO content pipeline: plan, write, gate-check, publish to WordPress, submit to search, and monitor AI visibility.

What it does
A local MCP server exposing 29 tools across workspace, site, article, check, publish, plan, image, monitor, db, search, diagnose, util and standards groups. It supports content planning, writing and ingest, gate checks, WordPress publishing, search submission and GEO monitoring, backed by a single-file multi-tenant SQLite database by default or MySQL optionally. It also ships a CLI with 21 commands and an agent launcher.
When to use it
Worth adding when an assistant should produce and publish SEO/GEO content end to end for one or more sites, including quality gate checks and visibility monitoring. Less useful for one-off writing that does not need publishing or tracking.
Requirements
Runs locally via npm package @tengence/geo-mcp over stdio. Environment variables: DB_DRIVER (sqlite default or mysql), SITES_ROOT (root of per-site config and .env files), TENGENCE_GEO_HOME (runtime data directory, defaults to ~/.tengence/geo-mcp). Per-site WordPress credentials and tokens go in each site's .env; the HTTP transport needs GEO_MCP_TOKEN. Desktop only.
Before you install
Publishing and submission tools write to external sites, so review before letting an assistant publish. Site credentials and tokens are read from SITES_ROOT/ /.env, and the HTTP transport requires the GEO_MCP_TOKEN bearer secret. The optional MySQL backend is separate from production databases, but confirm which database DB_DRIVER points at before running writes.

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

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.2LatestOct 2, 2026