The com.productclank/productclank MCP server description indicates it supports campaigns to boost posts and launch community growth from an AI assistant. The provided details include OAuth authentication and credit-billed usage, suggesting the server integrates with external services that require an OAuth flow and bill by credits.

🛠️ Key Features

Boost posts
Launch community growth campaigns
OAuth authentication
Credit-billed usage

🚀 Use Cases

Running community growth campaigns via an AI assistant
Boosting posts through assistant-driven workflows

⚡ Developer Benefits

OAuth-based integration model
Clear credit-billing approach for usage tracking

⚠️ Limitations

No additional capabilities, tooling details, or API scope are provided in the available server data.

ProductClank MCP Server

Launch community growth campaigns from your AI assistant. ProductClank turns real communities (and their agents) into a distribution network — this MCP server lets Claude or any MCP client rally that network on your behalf: boost a post with real replies, likes, and reposts; launch community content campaigns; draft social content into your own pipeline.

Remote server: https://mcp.productclank.com/mcp (Streamable HTTP)
Auth: OAuth 2.1 — sign in with your ProductClank account, revoke anytime
Billing: your ProductClank credits, per-tool costs shown below, with per-app daily spend caps
Website: productclank.com/mcp

Connect from Claude

In Claude, add a custom connector with the URL:
code
```
https://mcp.productclank.com/mcp
```
Approve the OAuth prompt — it signs you into ProductClank (Google or email) and asks for consent.
Ask Claude things like:

"Boost this post with replies from the ProductClank community: https://x.com/…" "Preview a content campaign for my product." "What's my ProductClank credit balance?"

Works in any MCP client that supports remote servers with OAuth (Claude web/desktop, Claude Code, and others).

Tools

Tool	What it does	Cost
`search_products`	Resolve your ProductClank products to a `product_id` (required for campaigns)	free
`check_balance`	Your credit balance and plan	free
`boost_post`	Rally the community to engage a specific post — 10 AI-drafted replies (200 cr), 30 likes or 10 reposts (300 cr). Auto-detects platform from the URL: X, Instagram, TikTok, LinkedIn, Reddit, Farcaster	200–300 cr
`suggest_content_campaign`	AI-drafted preview of a community content campaign (title, description, CTA) + affordability check. Nothing is created	free
`create_content_campaign`	Launch the content campaign: the community creates posts/threads/videos for your product; submissions and winner selection happen in the web app	1,000 cr
`list_content_spaces`	Content Studio: list the content spaces you can draft into	free
`write_content_candidates`	Content Studio: draft up to 25 post candidates into your space. They land as unreviewed drafts — a human reviews and schedules; nothing auto-publishes	free

Costly actions are designed to be confirmed with the user first — tool descriptions instruct the model to preview and state the credit cost before spending.

How auth & billing work

The server is an OAuth 2.1 authorization server backed by the ProductClank web app (/connect/mcp login + consent). Every /mcp request requires a valid access token; tools act as the connected user and bill that user's credit balance. Users can see and revoke the connector — and set a daily credit spend cap per connected app — from their ProductClank profile ("Connected Apps").

Architecture

A thin Express + @modelcontextprotocol/sdk wrapper over ProductClank's public agent REST API (/api/v1/agents/*). The REST API is canonical; this server and the ProductClank agent skill are parallel wrappers — capabilities.json is the parity source of truth and CI fails when they drift (npm run check:parity).

code

Claude / MCP client ──▶ mcp.productclank.com/mcp (this server)
                          │  OAuth 2.1 AS ──▶ productclank.com/connect/mcp (login + consent)
                          └─▶ ProductClank agent REST API (/api/v1/agents/*)

Development

bash

cp .env.example .env   # fill in (see DEPLOYMENT.md)
npm install
npm run dev            # tsx watch
npm run typecheck
npm run build && npm start

See DEPLOYMENT.md for production deployment (Docker / Railway) and CAPABILITIES.md for the tool roadmap.

Registry

Published to the official MCP Registry as com.productclank/productclank — see server.json.

License

MIT

query	string	required	Product name or keyword to search for
limit	integer	optional	Max results (default 5)

url	string	optional	Product website URL — auto-fills the listing. Provide this or `name`.
name	string	optional	Product name. Optional if `url` is given (extracted from the site); required otherwise.
tagline	string	optional	One-line value proposition (optional; overrides extracted).
description	string	optional	Short description of what the product does (optional).
website	string	optional	Canonical website, if different from `url` (optional).
twitter	string	optional	X/Twitter handle or profile URL (optional).
logo	string	optional	Logo image URL (optional; otherwise auto-resolved from the site).
category	array	optional	Category tags (optional).

post_url	string	required	Full URL of the post to boost (any supported platform)
product_id	string	optional	Optional product UUID (from search_products or create_product). Omit for a tweet-first boost.
action_type	string	optional	How the community engages. Default: replies. Reposts are Twitter/Farcaster only.
reply_guidelines	string	optional	Optional guidance for the tone and content of community replies

product_id	string	required	Product UUID from search_products
campaign_message	string	required	The core brief: what you want the community to create (e.g. 'Share how you use <product> in your daily workflow').
campaign_goals	array	optional	Campaign goals, e.g. ["awareness", "signups"]
target_audience	string	optional	Who the campaign should reach
preferred_platform	string	optional	Preferred platform, e.g. "x" or "farcaster"
additional_guidelines	string	optional	Extra do's/don'ts for creators
references	string	optional	Links or references to include in the campaign

product_id	string	required	Product UUID from search_products
campaign_message	string	required	The core brief: what you want the community to create (e.g. 'Share how you use <product> in your daily workflow').
campaign_goals	array	optional	Campaign goals, e.g. ["awareness", "signups"]
target_audience	string	optional	Who the campaign should reach
preferred_platform	string	optional	Preferred platform, e.g. "x" or "farcaster"
additional_guidelines	string	optional	Extra do's/don'ts for creators
references	string	optional	Links or references to include in the campaign

ProductClank

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

search_products

create_product

check_balance

boost_post

suggest_content_campaign

create_content_campaign

list_content_spaces

write_content_candidates