INSSIST vs Pinsuite

A side-by-side look at the INSSIST and Pinsuite MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

INSSIST logoINSSISTSocial Media · Local subprocess (stdio)Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics.67GreatAuth: not declared
P
PinsuiteSocial Media
Download and save Pinterest boards, Instagram posts and web pages into a library you own.37FairAuth: not declared

Verdict: choose INSSIST for social media work as a local process; choose Pinsuite for social media. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

INSSIST logoChoose INSSIST when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: INSSIST_MCP_PORT, INSSIST_MCP_HOME.
  • You want tools like account_info, account_switch, antibot_export.
Explore INSSIST

P
Choose Pinsuite when

  • You need dedicated capabilities in the Social Media domain.
Explore Pinsuite

Feature & specification comparison

Rows where the two servers differ are marked.

SpecINSSIST logoINSSIST
P
Pinsuite
CategorySocial MediaSocial Media
Quality signal67/100 · Great37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingFreemiumNot declared
Required env varsINSSIST_MCP_PORTINSSIST_MCP_HOMENone listed
Verified ownerCommunity listingCommunity listing
GitHub stars31—
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools60Not listed

Tools & capabilities

INSSIST tools 60

  • account_infoList connected browser instances, the account each is logged into, other available accounts, and the default target. `proTrialDaysLeft` > 0 means PRO write tools answer for that many more days.
  • account_switchSwitch the browser profile to another logged-in account (see account_info). Later calls act as it; reloads open Instagram tabs. Switching to the active account is a no-op.
  • antibot_exportExport the full antibot follower analysis (risk + type per follower) to a CSV file; returns the path. (Requires INSSIST PRO.)
  • antibot_reportFollower quality analysis from the last antibot scan: totals by risk and type, plus the flagged (unreviewed high/medium-risk) followers. Empty until a scan has run. (Requires INSSIST PRO.)
  • antibot_scanStart a follower scan scoring each follower bot/suspicious/fresh/clean. Runs in the background; poll antibot_report. Detection only — removes no one. (Requires INSSIST PRO.)
  • comment_addPost a comment on a post. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comment_deleteDelete a comment — your own, or any on your own post. Permanent. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comment_likeLike a comment, or unlike with `unlike: true`. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comment_replyReply to a comment. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)
  • comments_listList comments on a post and their replies. (Requires INSSIST PRO.)
  • dm_acceptAccept a pending DM message request, moving it into the inbox. (Requires INSSIST PRO.)
  • dm_listList recent DM conversations, the last message, and whether a reply is awaited. Returns Instagram's single inbox page, which cannot be paged further. Read-only.
  • +48 more on the listing page

Pinsuite tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

INSSIST

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "inssist": {
      "command": "npx",
      "args": [
        "-y",
        "@inssist/mcp"
      ],
      "env": {
        "INSSIST_MCP_PORT": "YOUR_INSSIST_MCP_PORT_HERE",
        "INSSIST_MCP_HOME": "YOUR_INSSIST_MCP_HOME_HERE"
      }
    }
  }
}

Pinsuite

No confirmed install command for Pinsuite yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

INSSIST is categorized under Social Media and uses a local stdio subprocess. Pinsuite belongs to Social Media and uses an install path we have not confirmed yet. Pick INSSIST for social media work and Pinsuite for social media.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Pinsuite has no confirmed install command yet — follow its own setup instructions.

INSSIST is listed as freemium — a free tier with paid plans. Pinsuite has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add inssist and pinsuite as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, INSSIST has a quality signal of 67/100 (Great) with 1 views, 0 installs and 31 GitHub stars. Pinsuite has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.