InsightSocial MCP server

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.

search, company pages, jobs, ads and transcripts.

• 239 endpoints: profiles, public emails, posts, reels, comments, followers, likers, hashtags,

(post.url, post.engagement.likes, computed.engagement_rate).

• One schema across platforms: a TikTok video and an Instagram post come back with the same fields

free.

• Priced per endpoint, charged per call. Empty results, failed calls and idempotent replays are

a 50 KB page never ends up in your context.

• Built for agents. Every result is saved in full, and you re-slice it locally with jq for free, so

Quick start

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

Get a key at . 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 INSIGHTSOCIALAPIKEY 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 : 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

Shortened. The full README is on GitHub.