Citedy Seo Agent vs Tengence GEO Agent
A side-by-side look at the Citedy Seo Agent 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.
Verdict: choose Citedy Seo Agent for marketing work as a local process; 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?
Choose Citedy Seo Agent when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 56/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | GEO_MCP_TOKENSITES_ROOT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 20 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Citedy Seo Agent | View Tengence GEO Agent |
Tools & capabilities
Citedy Seo Agent 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.
Citedy Seo Agent
{
"mcpServers": {
"citedy-citedy-seo-agent": {
"command": "npx",
"args": [
"-y",
"openskills"
]
}
}
}
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
Citedy Seo Agent is categorized under Marketing and uses a local stdio subprocess. Tengence GEO Agent belongs to Marketing and uses a local stdio subprocess. Pick Citedy Seo Agent 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.
Citedy Seo Agent is listed as freemium — a free tier with paid plans. Auth: api key required. 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 citedy-citedy-seo-agent and tengence-geo-agent as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Citedy Seo Agent has a quality signal of 56/100 (Good) with 3 views, 0 installs and 20 GitHub stars. Tengence GEO Agent has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.