SEO Content Factory vs Tengence GEO Agent
A side-by-side look at the SEO Content Factory and Tengence GEO Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SEO Content FactoryMarketingDraft SEO blog articles from topic to ready-to-review post.36FairAuth: not declaredVerdict: choose SEO Content Factory for marketing work; choose Tengence GEO Agent for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose SEO Content Factory when
- You need dedicated capabilities in the Marketing domain.
Choose Tengence GEO Agent when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GEO_MCP_TOKEN, SITES_ROOT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SEO Content Factory | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 36/100 · Fair | 36/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GEO_MCP_TOKENSITES_ROOT |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View SEO Content Factory | View Tengence GEO Agent |
Tools & capabilities
SEO Content Factory tools
No tool names declared yet. Check the project README from the listing page.
Tengence GEO Agent tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SEO Content Factory
No confirmed install command for SEO Content Factory yet — follow the setup steps linked from its listing page rather than a guessed package name.
Tengence GEO Agent
{
"mcpServers": {
"tengence-geo-agent": {
"command": "npx",
"args": [
"-y",
"@tengence/geo-agent"
],
"env": {
"GEO_MCP_TOKEN": "YOUR_GEO_MCP_TOKEN_HERE",
"SITES_ROOT": "YOUR_SITES_ROOT_HERE"
}
}
}
}
Frequently asked questions
SEO Content Factory is categorized under Marketing and uses an install path we have not confirmed yet. Tengence GEO Agent belongs to Marketing and uses a local stdio subprocess. Pick SEO Content Factory for marketing work and Tengence GEO Agent for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. SEO Content Factory has no confirmed install command yet — follow its own setup instructions.
SEO Content Factory has no declared pricing — check the project's own site. Tengence GEO Agent has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add seo-content-factory and tengence-geo-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SEO Content Factory has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tengence GEO Agent has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.