AgentPixel vs SEOmatic
A side-by-side look at the AgentPixel and SEOmatic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AgentPixelMarketing · Remote HTTP/SSEConsent-first website pixel for AI agents. Your agent sets up a consent bar, installs the tag, verifies it and reads contacts. Hosted remote MCP server at https://agentpixel.io/mcp?src=allmcps (Streamable HTTP). try_sample works with no account or key.53GoodAuth: oauth 2.0Verdict: choose AgentPixel for marketing work over a hosted endpoint; choose SEOmatic for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose AgentPixel 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 SEOmatic 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 | A AgentPixel | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 53/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
Tools & capabilities
AgentPixel tools
No tool names declared yet. Check the project README from the listing page.
SEOmatic 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.
AgentPixel
{
"mcpServers": {
"agentpixel": {
"url": "https://agentpixel.io/mcp?src=allmcps"
}
}
}
SEOmatic
{
"mcpServers": {
"seomatic": {
"command": "npx",
"args": [
"-y",
"seomatic"
]
}
}
}
Frequently asked questions
AgentPixel is categorized under Marketing and uses a remote HTTP/SSE transport. SEOmatic belongs to Marketing and uses a local stdio subprocess. Pick AgentPixel for marketing work and SEOmatic 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.
AgentPixel is listed as a paid service. Auth: oauth 2.0. SEOmatic 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 agentpixel and seomatic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AgentPixel has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. SEOmatic has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.