MCP server exposing Instagram profile data as 5 agent tools — followers/following, specific list, network expansion, keyword & location discovery. Connect Claude Desktop, Cursor, ChatGPT to /mcp. Pay-per-profile pricing — $0.01 per analyzed profile. Same data + pricing as the parent scraper.
All notable changes to the Instagram Profile MCP Server actor are documented here.
The format follows Keep a Changelog .
[0.0.7] - 2026-05-08
Changed
Maintenance build — no user-facing changes.
[0.0.6] - 2026-05-07
Changed
README — refreshed structure for clarity (restored prior section layout). Same input, output, dataset shape, and pricing.
[0.0.5] - 2026-05-07
Changed
Maintenance build — no user-facing changes. Input schema, output dataset columns, KVS records, console output, error messages, defaults, and pricing are all unchanged from 0.0.4. Saved tasks continue to work identically.
[0.0.4] - 2026-05-07
Changed
README — aligned to Apify quality template (same shape as the parent and sibling actors). Hero rewritten with value-first prose and a "beyond what Instagram's official Graph API offers" comparison; numbered 3-step Quick start; new 🧭 When to use it (5 numbered scenarios); new ⭐ Choose your tool table covering all 5 MCP tools; new 💡 Tips & Best Practices section (4 sub-sections × 3 bullets); new 🛟 Support & feedback section pointing to Apify Store reviews / bookmark / Issues tab; new dedicated ⚖️ Is it legal to scrape Instagram? H2 with link to Apify's web-scraping legality blog; FAQ expanded from 5 to 10 Q&As (legality, ban risk, MCP vs regular run, Standby costs, agent auto-discovery, data freshness, cost cap). Section order normalized to match the family. No functional changes — same data, tools, pricing, schema.
[0.0.1] - 2026-05-07
Added
First public release. Instagram Profile MCP Server — wraps the Instagram Profile Scraper parent as a Model Context Protocol server with 5 narrow agent tools (Standby /mcp endpoint).
5 MCP tools, one per parent mode: instagram_analyze_followers_following (Mode 1), instagram_analyze_specific_accounts (Mode 2), instagram_network_expansion (Mode 3), instagram_keyword_discovery (Mode 4), instagram_location_discovery (Mode 5). Each tool exposes a narrow Zod schema (mode-specific required fields + a single filters / extraction object) so AI clients can pick by intent without inspecting the parent's 60-field INPUT_SCHEMA.
Hybrid input — actor accepts both Standby /mcp JSON-RPC tool calls and regular Apify run input (with operationMode + per-mode fields), so customers can use the same actor as MCP server OR as a one-shot run-input/output actor via Apify Console / apify call / API. Same 5 modes, same dataset shape on both paths.
Parent-parity data: 38-column dataset (Account, Source, Tagged Location, Matched By, Mutual Follow, Full Name, Followers Count, Bio, Email, Phone, External URL, Category, Reels Count, Median Views, Avg Likes, Avg Comments, Posts per Month, Median ER, Quality, Post 1–8, etc.). Mapping function populates every column using the same logic as parent.
Parent-parity pricing: PROFILE_ANALYZED $0.01 + USER_LIST_FETCHED $0.10 (Mode 1 only) — same FREE-tier prices as the parent scraper. Mirrors parent's tiered Console pricing 1:1.
Parent-parity FREE-plan paywalls: 50 profiles per run cap, 3 targets in Mode 1, 5 expansion profiles in Modes 3/4/5, masked emails (j***@a***.com), Reels analytics + view/follower ratio + searchDepth=2 paid-only. Each ceiling hit is recorded in FREE_LIMITS_APPLIED for transparency.
Test-run cap (≤$1) — when input matches a demo seed (natgeo / openai, claudeai / openai) at default with no maxCount, the run is capped at 10 profiles (~$0.10 trial cost) on any plan.
5 storage records mirroring the parent: RUN_SUMMARY, SKIPPED_ACCOUNTS, FREE_LIMITS_APPLIED, USER_MESSAGE, status.html. Standby instances aggregate counters across all MCP tool calls in the same instance and flush every 10 calls + on Actor.exit + on aborting.
All 4 Apify schemas + KVS schema wired in .actor/actor.json: input_schema.json, output_schema.json, dataset_schema.json, web_server_openapi.json (OpenAPI 3.0.3 for /mcp Streamable HTTP), key_value_store_schema.json.
Filter parity: every search filter the parent forwards (follower range, contact info, language, engagement, post-cadence, view/follower ratio, business category, AND/OR keyword combination) is supported in the wrapper.
