InsightSocial

insightsocial

The official CLI and MCP server for the InsightSocial API: live public data from 22 platforms through one key: TikTok, LinkedIn, YouTube, X, Reddit, Pinterest, Bluesky, Truth Social, Snapchat, Telegram, Twitch, Kick, Rumble, Kwai, Douyin, Xiaohongshu (RedNote), Quora, TikTok Shop, Weibo, Zhihu, Substack and Nextdoor.

• 230+ endpoints: profiles, public emails, posts, videos, comments, followers, likers, hashtags, search, company pages, jobs, ads, transcripts, shop products and local business listings.
• One schema across platforms: a TikTok video and a YouTube video come back with the same fields (post.url, post.kind, post.engagement.likes, post.language), and unavailable lists any field a response could not fill. The CLI and MCP server ask for schema 2 on every call.
• 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

npx -y insightsocial init              # sign in through your browser, install the agent skill, show MCP setup
npx -y insightsocial search tiktok followers
npx -y insightsocial run /v1/tiktok/profile -p handle=natgeo
npx -y insightsocial view --last --jq '.data.author | {username, followers}'

init and login sign you in through your browser: they open the sign-in page and print a short code, you type the code there and click Allow, and a key named after this machine is saved. The CLI then prints which account it signed into. To use a key you already have, pass --api-key. New accounts include free calls.

Use it from an AI agent

Claude Code plugin

/plugin marketplace add insightsocial/skills
/plugin install insightsocial@insightsocial

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)

claude mcp add insightsocial --scope user -- npx -y insightsocial mcp

{
  "mcpServers": {
    "insightsocial": { "command": "npx", "args": ["-y", "insightsocial", "mcp"] }
  }
}

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.

Nothing to install: the same tools are hosted at https://api.insightsocial.app/mcp. Claude, ChatGPT and other clients that support it sign in with OAuth; others send the key as Authorization: Bearer. See MCP docs.

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.

Pricing a call first: -p dry_run=1 (or true) on any endpoint returns the quote and charges nothing. When a response could not fill a field the platform normally has, run prints it under missing; that null means unknown, not zero.

Configuration

Develop

npm install
npm run check      # build + unit tests, no network and no key needed

License

MIT