Provides tools to search the Facebook / Meta Ad Library for active ad creatives by keyword or advertiser, including advertiser page, ad body text, media, platforms, run dates, and status.
Provides tools to retrieve recent Instagram posts with captions, media URLs, like/comment/play counts, and permalinks.
Provides access to the Meta Ad Library for searching active ad creatives from Meta platforms by keyword or advertiser.
Provides tools to retrieve TikTok creator profiles, including bio, verification, follower/following/like/video counts, and engagement stats.
Provides tools to list YouTube channel videos with view counts, publish dates, durations, and URLs, with sorting and pagination.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@scrapecreators Get the latest YouTube videos from ThePatMcAfeeShow"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ScrapeCreators MCP — wraps the ScrapeCreators social-media + ad-library
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tool | Description |
| Get a TikTok creator profile: bio, verification, follower/following/like/video counts, and engagement stats. Pass a TikTok handle/username (without the @) or a numeric user_id. Example: scrapecreators_tiktok_profile({ handle: "stoolpresidente", _apiKey: "your-key" }) |
| Get recent posts for an Instagram user: captions, media URLs, like/comment/play counts, and permalinks. Pass the Instagram username/handle. Use next_max_id to paginate. Example: scrapecreators_instagram_posts({ username: "nike", _apiKey: "your-key" }) |
| List videos for a YouTube channel with view counts, publish dates, durations, and URLs. Pass a channelId (UC...) or a channel handle. Sort by "latest" or "popular"; paginate with continuationToken. Example: scrapecreators_youtube_channel({ handle: "ThePatMcAfeeShow", _apiKey: "your-key" }) |
| Search the Facebook / Meta Ad Library by keyword or advertiser and return active ad creatives: advertiser page, ad body text, media, platforms, run dates, and active status. Example: scrapecreators_facebook_ads({ query: "running shoes", country: "US", _apiKey: "your-key" }) |
Related MCP server: Social MCP Connector
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"scrapecreators": {
"url": "https://gateway.pipeworx.io/scrapecreators/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/scrapecreators/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1576+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/scrapecreators_tiktok_profile. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"scrapecreators": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-scrapecreators"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-scrapecreatorsIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Scrapecreators data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Create, schedule, and publish social posts, manage accounts, and read analytics as MCP tools.
Social media MCP: publish, schedule & analyze posts on TikTok, Instagram, YouTube, LinkedIn & X
Search Meta, Google Ads, LinkedIn, and TikTok ad libraries plus creative analysis via MCP.
Get social media data from Instagram and TikTok: profiles, posts, videos, comments, and more.
