SEO Content Machine vs Tengence GEO Agent
SEO Content Machine is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
SEO Content Machine is a plugin bundle for AI coding tools published by SEO Content Machine. No marketplace we read lists it any more. Tengence GEO Agent is an MCP server published by tengence.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Tengence GEO Agent | |
|---|---|---|
| Community marketplace gitterebi/seo-content-machine-plugin | Removed on 2026-10-15 Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (npm): 773 Downloads/week (npm): 71 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | SEO Content Machineno longer listed · | Tengence GEO Agent |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@tengence/geo-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 0 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/gitterebi/seo-content-machine-plugin | github.com/tengence-team/tengence-geo-agent |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of SEO Content Machine
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.
-
AI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets
-
SEO content writing, planning, and quality auditing with E-E-A-T optimization
-
End-to-end SEO content pipeline connecting keyword research through to rank tracking. Validate and score keyword opportunities with DataForSEO, generate SERP-feature-targeted…
-
SEO content writing, planning, and quality auditing with E-E-A-T optimization
-
SEO content writing, planning, and quality auditing with E-E-A-T optimization
What each says it does
SEO Content Machine
Drive the SEO Content Machine desktop app from Claude Code: scraping, site crawls, Google Maps listings, archive.org downloads and SEO Workspace pages.
Tengence GEO Agent
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
How to run each
SEO Content Machine
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Tengence GEO Agent As a local MCP server: npm package
claude mcp add --transport stdio geo -- npx -y @tengence/geo-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only SEO Content Machine asks for
SCM_API_KEY (secret)SCM_API_URL
Only Tengence GEO Agent asks for
DB_DRIVERSITES_ROOTTENGENCE_GEO_HOME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: SEO Content Machine · What it can do: Tengence GEO Agent · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.