GEO by VibeSEO vs Optifeed Radar
A side-by-side look at the GEO by VibeSEO and Optifeed Radar MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GEO by VibeSEO for marketing work over a hosted endpoint; choose Optifeed Radar 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 GEO by VibeSEO when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Choose Optifeed Radar when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OPENAI_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 40/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | OPENAI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View GEO by VibeSEO | View Optifeed Radar |
Tools & capabilities
GEO by VibeSEO tools
No tool names declared yet. Check the project README from the listing page.
Optifeed Radar 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.
GEO by VibeSEO
{
"mcpServers": {
"aeo-geo-by-vibeseo": {
"url": "https://geo-mcp.vibeseo.dev/mcp"
}
}
}
Optifeed Radar
{
"mcpServers": {
"optifeed-optifeed-radar": {
"command": "npx",
"args": [
"-y",
"optifeed-radar"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
GEO by VibeSEO is categorized under Marketing and uses a remote HTTP/SSE transport. Optifeed Radar belongs to Marketing and uses a local stdio subprocess. Pick GEO by VibeSEO for marketing work and Optifeed Radar 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.
GEO by VibeSEO has no declared pricing — check the project's own site. Optifeed Radar is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 aeo-geo-by-vibeseo and optifeed-optifeed-radar as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GEO by VibeSEO has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Optifeed Radar has 53/100 (Good) with 3 views, 0 installs and 5 GitHub stars.