A side-by-side look at the Citedy Seo Agent and MCP Server 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 MCP Server 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.
No tool names declared yet. Check the project README from the listing page.
MCP Server 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 is categorized under Marketing and uses a local stdio subprocess. MCP Server belongs to Marketing and uses a local stdio subprocess. Pick Citedy Seo Agent for marketing work and MCP Server 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. MCP Server 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 liftaven-mcp-server 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. MCP Server has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.