Affset vs ProductClank — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Affset vs ProductClank
In-depth architectural comparison of the Affset and ProductClank MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Affset
Developer Tools · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
ProductClank
Developer Tools · Remote HTTP/SSE
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Affset if you need specialized Developer Tools tools running via a local process. Choose ProductClank if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Affset when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Show the tenant this server is bound to: namespace, API base, derived dashboard URL, and (when readable) company / timezone / custom API domain. Read-only.
get_stats
Traffic stats grouped by a dimension (date, campaign, zone, country, sub1–5, advertiser, publisher, …), optionally narrowed with `advertiser_email`/`publisher_email` filters (one user, any group_by). Returns clicks, conversions, CR, payout, media cost and ROI as a table. `paid_only` defaults to tru…
list_campaigns
List campaigns (status / name filter, pagination).
get_campaign
One campaign's full record — every field (untruncated offer URL, exact schedule, budgets/pacing, silent flag, payout goal type) plus its targeting rules and payout rules, in one call.
list_zones
List traffic-source zones (status / name filter, pagination, linked source).
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Affset is categorized under Developer Tools and uses a local stdio subprocess. In contrast, ProductClank belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Affset when you need capabilities focused on developer tools and ProductClank when you require tools for developer tools.
List team members (email, role, manager). **Never returns API tokens.
create_team_member
Invite a team member (owner, manager, publisher, advertiser, publisher_manager, advertiser_manager). A scoped manager key can only create its own managed role, self-assigned. Returns the new API key **once** — `list_team` never shows it again. **Dry-run by default**; `confirm: true` to apply.
create_campaign
Create a campaign from an advertiser email, offer URL, geo, payout and name. Defaults: CPA / rate 0, **paused**, global payout rule, and a ready tracking link (linked source template when configured; otherwise `source_click_id={clickid}` + sub placeholders). **Dry-run by default**; `confirm: true`…
set_campaign_status
Run** or **pause** a campaign (`action: "run" \
update_campaign
Partial update (name, offer URL, status, rate, budgets, dates, …). **Dry-run by default**; `confirm: true` to apply. Prefer `set_campaign_status` for run/pause.
create_zone
Create a traffic-source zone (name + optional postback/site/traffic-back URLs, optional `traffic_source_id` link). Always created `active`. **Dry-run by default**; `confirm: true` to apply.
update_zone
Partial update (name, status, URLs, `traffic_source_id`). **Dry-run by default**; `confirm: true` to apply. Pass `null` to clear a URL or unlink the source.
+17 more tools listed on main page
ProductClank Tools (27)
search_products
Resolve your ProductClank products to a `product_id
create_product
List a product from just its website URL (token-free listing, auto-filled)
create_campaign
Create a discovery campaign: continuously find relevant posts + draft community replies
run_research
Topic & competitor analysis — the free pre-flight before spending
generate_posts
Run discovery: scrape matching posts and draft a reply for each
AI-score posts against relevancy rules, prune the irrelevant (dry-run billed too)
regenerate_replies
Redraft selected replies with an edit request
get_campaign_activity
What's new since the last check — posts found, replies claimed, live links to what went out
get_campaign_results
Spend vs outcomes: the funnel, approval + survival rates, cost per usable reply
update_campaign
Merge keywords, enable the discovery sources research found, move the relevance bar, pause/resume, re-aim the platform targeting, change who posts the drafts
set_campaign_schedule
Put discovery on a schedule so it keeps finding conversations between sessions. Shows the projected daily cost and requires an explicit yes before enabling