Tengence GEO Agent runs on your own machine — the client starts it, so there is no endpoint to ping. 136 installs a week from npm. Last commit 12 Oct 2026.
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
We read the source, 3 d ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const res = spawnSync(process.execPath, [binPath, ...args], {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
const src = path.join(PRESETS_DIR, file);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add geo -- npx -y @tengence/geo-mcp
{
"mcpServers": {
"geo": {
"args": [
"-y",
"@tengence/geo-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.geo]
command = "npx"
args = ["-y", "@tengence/geo-mcp"]
{
"mcpServers": {
"geo": {
"args": [
"-y",
"@tengence/geo-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"geo": {
"args": [
"-y",
"@tengence/geo-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
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.).
The author declared them in the registry entry; get the values from the project itself.
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
GEO/SEO content engine: planning, writing, gate checks, WordPress publishing, GEO monitoring.
SEO, GEO & AI Visibility — research, write, optimize, publish & monitor content. 121 tools.
Monitor brand visibility, citations, competitors, sentiment, and GEO performance in AI search.
Continuous website testing by Validoria — monitor security, SEO, performance, and accessibility.
GEO visibility tests, score trends, sitemap discovery, and domain monitoring for AI agents.
Remote MCP server for hotel rate monitoring, parity checks, and pricing intelligence via Apify.
MCP server for Site Spy — lets AI agents monitor websites for changes
Answers built from our own checks of this server.