threads_posts — Social Media Data API MCP Tool
threads_posts
(threads posts) is one of 26 tools on the
Social Media Data API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call threads_posts from your client
- Claude Code Social Media Data API threads_posts run in your project directory
- Claude Desktop Social Media Data API threads_posts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Social Media Data API threads_posts ~/.cursor/mcp.json
- VS Code Social Media Data API threads_posts .vscode/mcp.json
- Zed Social Media Data API threads_posts ~/.config/zed/settings.json
- Windsurf Social Media Data API threads_posts ~/.codeium/windsurf/mcp_config.json
- Cline Social Media Data API threads_posts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Social Media Data API threads_posts ~/.gemini/settings.json
- Grok Social Media Data API threads_posts .mcp.json (in your project root)
- ChatGPT Social Media Data API threads_posts Settings → Connectors → Advanced → Developer mode
- Claude.ai Social Media Data API threads_posts Settings → Connectors → Add custom connector
- LangChain Social Media Data API threads_posts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http social-media-data https://social.duoleads.com/mcp
Other tools on this server
- bluesky_search
- bluesky_posts
- bluesky_profile
- hackernews_search
- hackernews_thread
- social_mentions
- x_search
- x_posts
- x_profile
- reddit_search
- reddit_comments
- tiktok_videos
- tiktok_search
- instagram_profile
- youtube_transcript
- youtube_comments
- facebook_ads
- social_search
- social_audience
- social_accounts
- linkedin_company
- people_search
- tiktok_followers
- tiktok_following
- linkedin_profile
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.