GEO MCP vs Hermoso
A side-by-side look at the GEO MCP and Hermoso MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GEO MCP for marketing work over a hosted endpoint; choose Hermoso 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 MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Choose Hermoso when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5,749 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View GEO MCP | View Hermoso |
Tools & capabilities
GEO MCP tools
No tool names declared yet. Check the project README from the listing page.
Hermoso 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 MCP
{
"mcpServers": {
"google-ads-meta-ads-seo-geo-mcp": {
"url": "https://connector.get-ryze.ai/mcp"
}
}
}
Hermoso
{
"mcpServers": {
"hermoso-ai-hermoso": {
"command": "npx",
"args": [
"-y",
"hermoso"
]
}
}
}
Frequently asked questions
GEO MCP is categorized under Marketing and uses a remote HTTP/SSE transport. Hermoso belongs to Marketing and uses a local stdio subprocess. Pick GEO MCP for marketing work and Hermoso 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 MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. Hermoso is listed as freemium — a free tier with paid plans. 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 google-ads-meta-ads-seo-geo-mcp and hermoso-ai-hermoso as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GEO MCP has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 5,749 GitHub stars. Hermoso has 56/100 (Good) with 2 views, 0 installs and 2 GitHub stars.