Tengence GEO Agent

io.github.tengence-teamPublished by GitHub account tengence-teamv0.1.1Updated Nov 10, 2026

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

VerifiedSTDIODesktop onlyProductivity & WorkflowWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

GEO/SEO content pipeline server that lets an assistant plan, write, gate-check, publish to WordPress, submit to search engines and monitor AI visibility.

What you can do
  • Manage workspaces and per-site configuration, including switching the active site at runtime
  • Ingest, draft and gate-check articles against shipped GEO writing standards
  • Publish content to WordPress and submit it to search engines
  • Plan content, handle images, and monitor AI visibility
  • Inspect and diagnose the storage backend and search utilities
When to use it
Use it when you run multi-site SEO/GEO content operations and want an assistant to carry an article from planning through drafting, quality checks, WordPress publishing and search submission, then track visibility.
Requirements
Runs locally over stdio from the npm package @tengence/geo-mcp, so Node.js is needed. A sites root directory (SITES_ROOT) holds per-site config and .env files with WordPress credentials and tokens; DB_DRIVER selects sqlite (default) or mysql; TENGENCE_GEO_HOME sets the runtime data directory. The optional HTTP transport requires a bearer token.
Before you install
Publishing and search submission write to external systems, so review drafts and gate results before pushing live. WordPress credentials and tokens live in per-site .env files under SITES_ROOT and should stay out of version control. The optional agent launcher needs a DEEPSEEK_API_KEY. MySQL mode writes to tengence_geo_* tables.

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 02fe3f3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.1LatestSep 27, 2026
  2. v0.1.0Sep 27, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts