ProductClank is a remote MCP server that gives an AI agent 30 tools, among them add_delegate, boost_post, check_balance. It answers at https://mcp.productclank.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Boost posts and launch community growth campaigns from your AI assistant. OAuth, credit-billed.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_delegate | Add a ProductClank user as a delegate on a campaign so they can view and manage it from the webapp's My Campaigns page. Free. Useful to hand oversight of an agent-created campaign to its human owner (the connected user's own id works too). Inputs: campaign_id, user_id |
boost_post | Rally the ProductClank community to engage with a specific social post. Creates a boost campaign and spends the user's credits: 'replies' generates 10 AI reply drafts (200 credits); 'likes' (30 likes) and 'repost' (10 reposts) cost 300. Sup Inputs: post_url, product_id, action_type, reply_guidelines |
check_balance | Return the connected user's ProductClank credit balance and plan. Use before launching a campaign to confirm they have enough credits (a content campaign costs 1000; a reply boost 200; likes/reposts 300; a discovery campaign 10 to create + |
create_campaign | Create a Communiply discovery campaign: it continuously finds relevant social posts (by keyword) and drafts replies that mention the product. BEFORE calling: the keywords and search_context are YOURS to derive, and deriving them well is mos Inputs: product_id, title, keywords, search_context, mention_accounts, reply_style_tags |
create_content_campaign | Launch a content campaign: rally the ProductClank community to create content (posts, threads, videos) for a product. Spends 1000 credits. The platform's AI expands your brief into a full campaign and auto-activates it; community submission Inputs: product_id, campaign_message, campaign_goals, target_audience, preferred_platform, additional_guidelines |
create_product | List a new product on ProductClank as a token-free listing (no crypto/token, no wallet). At minimum pass a `url` — the server auto-fills the name, tagline, description, logo, and X handle from the site; any field you pass explicitly overrid Inputs: url, name, tagline, description, website, twitter |
credit_history | The connected user's credit transactions (purchases, campaign spend, participation rewards), newest first. Free, read-only. Use to account for what this connector has spent or earned. Top-ups are NOT available in-connector — send the user t Inputs: limit, offset |
find_open_campaigns | Discover content and take-action campaigns the connected user can join and earn from: every active public campaign plus campaigns from communities the user belongs to. Each item has a kind — 'content' (create a post/thread/video about the p Inputs: limit, kind |
find_opportunities | Browse unclaimed reply drafts from active campaigns the connected user can earn from: each item is a real social post plus a pre-drafted reply, with the `platform` it lives on (X, Reddit, YouTube, LinkedIn). Free, read-only. Flow: pick an o Inputs: limit, offset, campaign_id |
generate_posts | Run the campaign's discovery pipeline: scrapes social platforms for posts matching the keywords and drafts a community reply for each. Costs 12 credits PER POST discovered (a typical run finds 5–20 posts, so 60–240 credits) and can take a f Inputs: campaign_id |
get_campaign | Get one campaign's configuration (keywords, search context, reply settings) plus live stats: posts discovered, replies by status. Free. Use to check progress after generate_posts or before adjusting the campaign. Inputs: campaign_id |
get_campaign_activity | Catch up on a campaign since the last check: posts discovered, replies claimed by community members, LIVE links to what they actually posted, and the engagement those replies drew. Free, and it never scrapes — safe to call at the start of e Inputs: campaign_id, since, limit |
get_campaign_brief | The full brief for one campaign: what to create or do (action message, brief sections, content types), how submissions are judged (eligibility + selection criteria), rewards, deadline, and how many submissions the user has left. Free, read- Inputs: campaign_id |
get_campaign_results | The cumulative scorecard for a campaign: the funnel (posts discovered → kept → replies drafted → claimed → posted → approved), the approval rate, whether posted replies survived on-platform, the engagement they drew, total credits spent bro Inputs: campaign_id |
get_earnings | The connected user's participation totals: points, credit balance, and reply stats (submitted / approved / rejected / strikes) for work submitted through this connector. Free, read-only. |
get_my_submissions | The connected user's submissions to one campaign: pending / approved / rejected, with the reviewer's notes. Free, read-only. Use to report outcomes back to the user after submit_campaign_work. Inputs: campaign_id |
get_posts | Read a campaign's discovered posts with their drafted replies. Free. Use after generate_posts to inspect what was found, then review_posts / regenerate_replies to refine. Inputs: campaign_id, limit, offset, status, include_replies |
get_research | Read the cached topic/competitor analysis for a campaign (from run_research). Free. Also reports which of its findings the campaign is actually searching: expanded keywords and exclusion terms always apply, while phrases / influencer accoun Inputs: campaign_id |
list_campaigns | List ALL the connected user's discovery/boost campaigns, newest first — including ones created in the ProductClank web app, not just via this connector. Free. Use to find a campaign id before get_campaign / generate_posts / get_posts. Inputs: limit, offset, status |
list_content_spaces | List the ProductClank content spaces you can draft into — spaces the user owns, delegates for, or manages that have their content engine turned on. Returns { space_id, name }. Call this first to resolve the space_id for write_content_candid |
regenerate_replies | Redraft the replies of specific posts with an edit request (e.g. 'shorter, no emojis, lead with the user's problem'). Costs 5 credits per reply regenerated; already-claimed replies are refused. Get post ids from get_posts. Confirm the spend Inputs: campaign_id, post_ids, edit_request |
review_posts | Score every discovered post against relevancy rules and delete the irrelevant ones (kept when dry_run:true). Costs 2 credits per post reviewed — dry runs are billed too, since the AI review runs either way. Start with dry_run:true to previe Inputs: campaign_id, review_rules, threshold, dry_run |
run_research | FREE pre-flight before spending credits: analyzes the campaign's keywords/topic and returns expanded keywords, high-intent phrases, influencer accounts, relevant X lists, and competitors. The EXPANDED KEYWORDS and exclusion terms are applie Inputs: campaign_id, force |
search_products | Search the user's ProductClank products by name and return their IDs. A product_id is required to create or boost a campaign — use this to resolve it, then confirm the match with the user. Inputs: query, limit |
set_campaign_schedule | Turn standing discovery on or off for a campaign. Calling this is free, but switching it ON authorizes spend that happens LATER and unattended: an hourly job runs discovery on its own and bills the user 12 credits per post it finds, with no Inputs: campaign_id, enabled, frequency_per_day, posts_per_run, confirmed |
submit_campaign_work | Submit the user's work for a campaign. Three ways to prove it, and any one is enough: proof_url (content they published or an action they took), media_url (a hosted image or video made for the task — the ad-hoc creative case: a demo clip, a Inputs: campaign_id, proof_url, media_url, description |
submit_participation | Submit the URL of a reply the connected user posted for a claimed opportunity (reply_id from find_opportunities). Works for X, Reddit, YouTube and LinkedIn replies. Every claim is attributed to the user's linked handle for that platform, so Inputs: reply_id, reply_url |
suggest_content_campaign | Preview a content campaign for a product BEFORE launching it. FREE — nothing is created and no credits are charged. Returns an AI-drafted campaign (title, description, call-to-action) plus whether the user can afford to launch it (1000 cred Inputs: product_id, campaign_message, campaign_goals, target_audience, preferred_platform, additional_guidelines |
update_campaign | Adjust a live campaign without recreating it. Free — nothing here spends credits, though the next generate_posts run bills as usual. Keywords MERGE (add_keywords never drops what is already there). `sources` is how research findings get app Inputs: campaign_id, add_keywords, remove_keywords, sources, monitor_accounts, relevance_threshold |
write_content_candidates | Draft one or more content candidates into a ProductClank content space. FREE — no credits charged. Candidates land as UNREVIEWED DRAFTS in the builder's 'All Content' queue; a human reviews, edits, and schedules them — nothing is auto-publi Inputs: space_id, candidates |
Every block below points at https://mcp.productclank.com/mcp. Pick your client and copy.
claude mcp add --transport http productclank https://mcp.productclank.com/mcp
{
"mcpServers": {
"productclank": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.productclank.com/mcp"]
}
}
}{
"mcpServers": {
"productclank": {
"url": "https://mcp.productclank.com/mcp"
}
}
}{
"servers": {
"productclank": {
"type": "http",
"url": "https://mcp.productclank.com/mcp"
}
}
}{
"context_servers": {
"productclank": {
"url": "https://mcp.productclank.com/mcp"
}
}
}{
"mcpServers": {
"productclank": {
"serverUrl": "https://mcp.productclank.com/mcp"
}
}
}{
"mcpServers": {
"productclank": {
"url": "https://mcp.productclank.com/mcp"
}
}
}name: ProductClank
version: 0.0.1
schema: v1
mcpServers:
- name: ProductClank
type: streamable-http
url: https://mcp.productclank.com/mcp{
"mcpServers": {
"productclank": {
"httpUrl": "https://mcp.productclank.com/mcp"
}
}
}{
"mcpServers": {
"productclank": {
"type": "http",
"url": "https://mcp.productclank.com/mcp"
}
}
}{
"mcpServers": {
"productclank": {
"url": "https://mcp.productclank.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.productclank.com%2Fmcp&type=streamable_http&id=productclank&name=ProductClank
It answered our last check on 18 October 2026 in 350 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by productclank.com and served from mcp.productclank.com, the vendor's own domain: https://mcp.productclank.com/mcp.
30, as returned by the server's own tools/list on 31 August 2026: add_delegate, boost_post, check_balance, create_campaign, create_content_campaign, create_product, credit_history, find_open_campaigns, and 22 more.
It answered our last check on 18 October 2026 in 350 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.productclank.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.productclank. Endpoint host: mcp.productclank.com. ARD identifier: urn:air:com.productclank:mcp:productclank.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.