
InsightSocial
app.insightsocialv0.1.0Updated Oct 3, 2026
Live public data from Instagram, TikTok, LinkedIn, YouTube, X and 4 more networks, via one key.
Overview
Lets an assistant search and call 239 paid InsightSocial endpoints for live public social media data across nine networks.
- What it does
- Exposes the InsightSocial API as MCP tools: search_endpoints and describe_endpoint find and explain endpoints for free, call_endpoint fetches data and saves the full response while returning a trimmed view with a result_id, read_result re-slices saved results locally with jq, and get_credits reports balance and usage. It covers profiles, public emails, posts, reels, comments, followers, likers, hashtags, search, company pages, jobs, ads and transcripts, with one shared schema across platforms.
- When to use it
- Use it when an assistant needs live public data from Instagram, TikTok, LinkedIn, Facebook, YouTube, X, Reddit, Threads or Pinterest, such as profile lookups, engagement metrics, hashtag or keyword search, or transcripts. It suits agent workflows that want to inspect large responses locally instead of loading them into context.
- Requirements
- Runs locally over stdio via npx (Node.js required). An InsightSocial API key is needed for data calls, supplied through the INSIGHTSOCIAL_API_KEY environment variable, the --api-key option, or the config file written by login; search and describe work without a key. Network access to the InsightSocial API is required, and the key is checked against the service.
Installation
In SourceWeft
- Open InsightSocial in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
insightsocial
The official CLI and MCP server for the InsightSocial API: live public data from Instagram, TikTok, LinkedIn, Facebook, YouTube, X, Reddit, Threads and Pinterest through one key.
- 239 endpoints: profiles, public emails, posts, reels, comments, followers, likers, hashtags, search, company pages, jobs, ads and transcripts.
- One schema across platforms: a TikTok video and an Instagram post come back with the same fields
(
post.url,post.engagement.likes,computed.engagement_rate). - Priced per endpoint, charged per call. Empty results, failed calls and idempotent replays are free.
- Built for agents. Every result is saved in full, and you re-slice it locally with jq for free, so a 50 KB page never ends up in your context.
Quick start
Get a key at https://www.insightsocial.app/portal/api/keys. New accounts include free calls.
Use it from an AI agent
Claude Code plugin
This installs the skill and the MCP server together, from
insightsocial/skills. Run npx -y insightsocial login once so
the server can find your key.
MCP server (any client)
The server reads the key saved by insightsocial login, so the config holds no secret. You can
also pass INSIGHTSOCIAL_API_KEY in its env. Without a key, search and describe still work.
insightsocial init --yes writes the MCP entry into Claude Code, Codex and Cursor for you.
Commands
Shaping flags (run and view) trim only what is printed; the saved file is always complete:
--jq <expr>: real jq (bundled, nothing to install) over the saved response. Paths start at.data.--fields a,b.c: keep these keys on each item. Dotted paths descend.--max-items N: show at most N items.--summary: the structure with byte sizes, so you can see what is large before pulling it.
Paging: when there is another page, run prints the exact next command. Each page is a
separate charged call.
Configuration
Develop
License
MIT
Source: README.md at commit 59881fe
Tools
0Version history
1- v0.1.0LatestOct 3, 2026


