Placement API vs SEOmatic
A side-by-side look at the Placement API and SEOmatic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Placement API for marketing work over a hosted endpoint; choose SEOmatic 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 Placement API when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
PLACEMENT_KEY. - You want tools like
search_placements, plan_links, compare_domain.
Choose SEOmatic 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 | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 48/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | PLACEMENT_KEY | None listed |
| Verified owner | Community listing |
Tools & capabilities
Placement API tools 5
search_placementsSearch ~550k priced placements deduplicated by domain, with verification, score and price plausibility on every rowplan_linksA brief in (links, topic, DR, budget, strategy) → a costed plan of named domains, each with `why`, held at price for four hourscompare_domainEverything about one publisher: listings and spread, verification, web-graph, survival, outcomes, Placement Score, market referencetarget_profileYour page's backlink profile and the competitor links you can reproducibly buy, pricedkeyword_winnersWhat the sites that rank for a keyword look like, and what they buy
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.
Placement API
{
"mcpServers": {
"placement-api": {
"url": "https://api.placementapi.com/mcp"
}
}
}
SEOmatic
{
"mcpServers": {
"seomatic": {
"url": "https://app.seomatic.ai/api/mcp"
}
}
}
Frequently asked questions
Placement API is categorized under Marketing and uses a remote HTTP/SSE transport. SEOmatic belongs to Marketing and uses a remote HTTP/SSE transport. Pick Placement API 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.
Placement API has no declared pricing — check the project's own site. 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 placement-api and seomatic as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Placement API has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. SEOmatic has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.