How do I install Tengence GEO Agent?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Tengence GEO Agent need an API key?

The publisher lists these environment variables: SITES_ROOT, TENGENCE_GEO_HOME, DB_DRIVER.

What transport does Tengence GEO Agent use?

Tengence GEO Agent runs locally over stdio.

When was Tengence GEO Agent last checked?

Last checked 2026-11-10. GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.

Tengence GEO Agent MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @tengence/[email protected]

Credentials from the publisher

SITES_ROOT — Root directory holding per-site config and .env files. Optional; the workspace is chosen at runtime via the workspace_use tool.
TENGENCE_GEO_HOME — Internal runtime data directory (DB, caches). Defaults to ~/.tengence/geo-mcp.
DB_DRIVER — Storage backend: sqlite (default) or mysql for production.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1SITES_ROOT=<value> TENGENCE_GEO_HOME=<value> DB_DRIVER=<value> claude mcp add io.github.tengence-team-geo -- npx -y @tengence/geo-mcp@0.1.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.tengence-team-geo": {4      "command": "npx",5      "args": [6        "-y",7        "@tengence/[email protected]"8      ],9      "env": {10        "SITES_ROOT": "<value>",11        "TENGENCE_GEO_HOME": "<value>",12        "DB_DRIVER": "<value>"13      }14    }15  }16}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.1.1

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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)

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

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

Documentation

Architecture & design decisions (layering / multi-tenancy / init model / why MCP bridging)

Generic writing & GEO standards — shipped in @tengence/geo-sdk, consumed via the MCP resources geo://standard-index / geo://standard/{name} and the article_draft tool (the requirements an article must satisfy)

Getting started

MCP integration (stdio / HTTP, any client)

Release & distribution (npm / Docker)

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