site-studio vs Tengence GEO Agent
site-studio is a plugin bundle for AI coding tools published by Ayan Gupta. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). 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-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Tengence GEO Agent | |
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.0.2 Forks (GitHub): 5 114 Stars (GitHub): 39 983 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (npm): 746 Downloads/week (npm): 130 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 | site-studio | Tengence GEO Agent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 39 983 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 5 114 (better) | 0 (worse) |
| 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) | Not published | 3, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/github/awesome-copilot | github.com/tengence-team/tengence-geo-agent |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
site-studio
Plan, draft, and track a personal website section by section — a shared canvas where you and your agent author content, watch progress, and review every change.
Tengence GEO Agent
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
How to run each
site-studio
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
The marketplaces of site-studio publish no settings it asks for, so we do not compare settings.
What it can do: site-studio · What it can do: Tengence GEO Agent · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.