Citedy Seo Agent vs ClearPost: WordPress SEO Agent
A side-by-side look at the Citedy Seo Agent and ClearPost: WordPress SEO Agent MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
ClearPost: WordPress SEO AgentMarketing · Remote HTTP/SSESEO agent for WordPress. Grows your organic traffic on autopilot. 12 tools, zero configuration.42FairAuth: not declaredVerdict: choose Citedy Seo Agent for marketing work as a local process; choose ClearPost: WordPress SEO Agent for marketing over a hosted endpoint. 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.
CChoose ClearPost: WordPress SEO Agent when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C ClearPost: WordPress SEO Agent | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 56/100 · Good | 42/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 20 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Citedy Seo Agent | View ClearPost: WordPress SEO Agent |
Tools & capabilities
Citedy Seo Agent tools
No tool names declared yet. Check the project README from the listing page.
ClearPost: WordPress SEO 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"
]
}
}
}
ClearPost: WordPress SEO Agent
{
"mcpServers": {
"clearpost-wordpress-seo-agent": {
"url": "https://clearpostplugin.com/mcp"
}
}
}
Frequently asked questions
Citedy Seo Agent is categorized under Marketing and uses a local stdio subprocess. ClearPost: WordPress SEO Agent belongs to Marketing and uses a remote HTTP/SSE transport. Pick Citedy Seo Agent for marketing work and ClearPost: WordPress SEO 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. ClearPost: WordPress SEO 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 clearpost-wordpress-seo-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. ClearPost: WordPress SEO Agent has 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.