Social Media
fetchwire.dev
A social media MCP server that retrieves user profiles, posts, comments, and search results across platforms like YouTube, TikTok, Instagram, X, and Reddit.
ENDPOINT 1
https://mcp.fetchwire.dev/mcp
MCP server metadata
- Name
- fetchwire
- Version
- 0.1.0
Fetchwire returns public profiles, posts, and comments from YouTube, TikTok, Instagram, X, Reddit, LinkedIn, and Threads as one JSON schema, so the same fields come back whichever platform you ask. Start with the operation tools: get_user, get_user_posts, get_post, get_comments, search_posts, search_users. Each takes a `platform` and accepts handles, ids, or public URLs for `id` — pass whatever you have, it is parsed for you. For anything outside those six operations (TikTok's shop and live data, Reddit's subreddits, LinkedIn's jobs, Instagram's hashtags and places), call list_routes to see what exists and call_route to fetch it. Every call spends credits from the account behind the API key, so prefer one precise request to several speculative ones. list_routes and get_usage are free; check get_usage if you are unsure of the balance. Lists page with `cursor`: pass the `next_cursor` from a response to get the next page, and stop when it is null.
Known tools 10
get_userA user's profile on any platform: follower counts, bio, verification, and platform extras under `extra`.
Inferred read-onlyget_commentsComments on a post, flat, with `parent_id` set on replies so the tree is one pass to rebuild.
Potential side effectssearch_postsSearch posts or videos by keyword on youtube, tiktok, instagram, x, or reddit.
Inferred read-onlysearch_usersFind accounts by name or keyword on youtube, tiktok, instagram, x, reddit, or threads.
Inferred read-onlycall_routeFetch any Fetchwire route by path, for the routes the operation tools do not cover.
Inferred read-onlylist_platformsThe platforms Fetchwire serves and which of the six operations each one supports.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.fetchwire]
url = "https://mcp.fetchwire.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"fetchwire": {
"type": "http",
"url": "https://mcp.fetchwire.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: fetchwire
Remote MCP URL: https://mcp.fetchwire.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"fetchwire": {
"url": "https://mcp.fetchwire.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"fetchwire": {
"type": "http",
"url": "https://mcp.fetchwire.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "fetchwire",
"transport": "streamable-http",
"url": "https://mcp.fetchwire.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.