4 ways to connect Instagram to Claude in 2026 (without getting banned)

Connect Instagram to Claude with MCP

For this tutorial we’re going with the MCP method. Here’s a quick explainer of what MCP is and why it’s the best path for Instagram.

MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, Claude Code and others access and use external APIs — the things that make tools like Instagram work under the hood. Instead of building a custom integration for every AI tool you use, you install one MCP and every compatible AI gets access to the same data.

• 📋 Copy-paste setup — No tokens, no scripts, no developer help — literally paste one URL into Claude and you’re done.
• 🔌 Works with every AI tool — Claude, Claude Code, ChatGPT, Cursor, Antigravity, Lovable, Vercel v0, Zapier. One MCP URL, every tool that speaks the protocol.
• 🔀 20+ sources in one connection — Porter’s MCP ships Instagram plus Google Ads, GA4, Shopify, HubSpot, Klaviyo, Google Sheets and 20+ more. Query and blend them all in a single conversation.
• 🎛️ Perfect granularity — Spreadsheets lock you into the columns you exported. MCP hits Meta’s API directly — so you can filter by post type, break down by date or media product type, and add new dimensions on the fly without rebuilding tables.

The full setup takes under 5 minutes and breaks into three moves: connect Instagram to Porter, point Claude at the Porter MCP, and ask your first question.

1. Connect your Instagram data to Porter {#mcp-connect}

Porter sits between Meta’s Graph API and Claude. It handles OAuth, rate limiting, pagination and all the plumbing so Claude only ever sees clean, structured data.

Sign up for Porter. Create a free account at portermetrics.com. The free tier is enough to run this full workflow end-to-end.

Connect your Instagram Business profile. In Porter, click Create → pick Claude as the destination → select Instagram as the source → sign in with Instagram to grant access to your accounts.

Select your accounts. Choose the Instagram accounts you want Claude to query. When you select multiple accounts under a single connection, Porter automatically blends their data together so you can query them as one.

Optional: enable automatic BigQuery storage if you’re connecting multiple accounts with large data volumes. This keeps Claude’s responses fast even at scale.

2. Connect the MCP to Claude {#mcp-claude}

Porter’s MCP URL is what you paste into Claude. Once added, Claude can query Instagram data on demand in any conversation.

Go to claude.ai and click the + icon in the chat input to open the tools menu.

!Click the + icon in the Claude chat input

In the menu that opens, hover over Connectors and click Manage connectors.

!Hover Connectors and click Manage connectors

In the Connectors panel, click the + button at the top of the list to start adding a new connector.

!Click + at the top of the Connectors panel

Pick Add custom connector from the dropdown that appears.

!Select Add custom connector from the dropdown

A dialog opens with the name and URL fields. Type Porter in the first field to name the connector.

!Type Porter in the connector name field

In the second field, paste https://mcp.portermetrics.com/mcp. Leave the advanced settings alone.

!Paste the Porter MCP URL into the Remote MCP server field

Click Add at the bottom right of the dialog. Claude opens a sign-in window — use the same Google account linked to your Porter workspace and approve access.

!Click Add on the custom connector dialog

Once the authorization finishes, you’ll see Porter’s read-only tools appear in the connectors panel. You’re ready to start asking questions.

!Porter read-only tools visible in the Claude connectors panel

For a fuller walkthrough with screenshots at every step, see the Porter MCP tutorial.

3. Start building questions and dashboards {#mcp-ask}

With Porter connected, open a new Claude chat and ask anything about your Instagram in plain English. Claude calls Porter behind the scenes, pulls live data from Meta, and answers with tables, charts, or summaries.

Try one of these to verify the setup is working:

For a full catalogue of copy-paste prompts organized by use case (performance, fatigue, budget, agency, brand teams, creators, cross-channel), jump to the prompts section below.

Alternative ways to connect Instagram to Claude

MCP is the path we just walked through — and the one we recommend for most marketers. But it’s not the only way to get Instagram data in front of Claude. The most common alternatives are Instagram’s direct API (or its official MCP if it has one), a live Google Sheets bridge, and BigQuery for scale. Each has its trade-offs — pick the one that fits how your team already works.

• 🔌 Instagram’s direct API (or official MCP) — Talk to Meta’s Graph API yourself, or install an official Instagram MCP if one exists. Maximum control, but you handle auth, rate limits and pagination — and you only get one source.
• 📊 Google Sheets — Live Sheet or one-off CSV upload. Auditable, familiar, faster for big exports — but aggregation happens in the Sheet, not the API.
• 🗄️ Google BigQuery — For large accounts or agencies running multi-account analysis. BigQuery aggregates; Claude only queries pre-built summaries.

Via Instagram’s direct API (or official MCP) {#via-api}

If you’re building a product around Instagram — or you’re a developer who’d rather own every layer of the integration — the most direct path is talking to Meta’s Graph API yourself, or installing an official Instagram MCP (if one exists). Meta doesn’t ship an official Instagram MCP yet, so this means writing API calls directly in Claude Code or in your own scripts. You’ll need to follow Meta’s rate limits & quotas and request a Developer Token / API access where applicable. Either way, you skip Porter entirely and call Meta from your own code or from Claude Code with raw HTTP requests.

Via Google Sheets (live Sheet or manual CSV) {#via-sheets}

If your team already lives in Google Sheets — or you want a paper trail before Claude touches anything — feed Instagram into a Sheet, then let Claude read the Sheet. You can automate the Instagram → Sheets pipeline with Porter so it refreshes daily, or do one-off CSV exports from Instagram’s native UI for static analysis.

Via Google BigQuery (for scale) {#via-bigquery}

This is the path most people overlook — and it’s the one that saves you when your Instagram account gets serious. A single large marketer or an agency managing 10+ accounts will hit API rate limits and latency problems querying Claude directly. Claude will literally tell you it’s taking too long or timing out on big pulls.

BigQuery fixes that. You load Instagram data into BigQuery tables on a schedule, then connect BigQuery to Claude — either through a BigQuery MCP or via Claude Code with SQL queries. Instead of asking Claude to pull raw Instagram data, you let BigQuery aggregate into small, optimized tables, and Claude only queries the summarized output. Scale problem solved.

Connecting Instagram to Claude Code

Most marketers lump Claude and Claude Code together and miss the biggest advantage of the entire MCP ecosystem. They’re not the same tool — and the difference matters enormously once you start working with Instagram data seriously.

Claude is a chat interface. You ask a question, Claude pulls live data through the MCP, answers, maybe builds a quick dashboard inside the conversation. Great for one-off analysis. The problem: everything is ephemeral. Want to refresh the dashboard tomorrow? You regenerate it from scratch. Want the same report every Monday? You re-ask the question every Monday.

Claude Code is Claude running inside your computer’s terminal. Because it has access to your filesystem, runtime, and other developer tools, it doesn’t just answer questions — it can build real software. Persistent scripts, scheduled routines, HTML apps, internal dashboards, integrations that run 24/7 without your input. Once it’s connected to Porter’s MCP for Instagram, a whole category of work becomes possible.

What Claude Code unlocks that Claude alone cannot {#claude-code-unlocks}

This is where the MCP ecosystem pays off most. Because Claude Code can combine Porter’s MCP with other MCPs — Firecrawl for web scraping, Airtable for structured data, Notion for wikis, Vercel for deployment, Slack and Gmail for delivery — you’re no longer querying data. You’re building tools.

🛠️ Build your own Instagram analytics dashboard Stack: Porter MCP + Vercel MCP (or Cloudflare Pages, Netlify) Feed Claude Code your Instagram targets and goals — engagement rate goals, follower growth targets, content performance benchmarks — and ask it to generate a custom engagement and reach dashboard for each client. It builds the HTML, pulls live data, deploys to a URL. No Data Studio embed to break when the vendor changes pricing, no template constraints. The dashboard updates automatically because it queries Porter’s MCP on every page load. Best for: agencies that want white-label client dashboards without Looker or Data Studio dependencies.

🔍 Full competitor + performance monitoring Stack: Porter MCP + Firecrawl MCP Combine your own Instagram performance from Porter with competitor Instagram profiles and trending hashtags from public sources scraped via Firecrawl. Claude Code stitches both into a weekly competitive intelligence report — your numbers next to their content angles and posting frequency, with an LLM summary on top of what changed week over week. Runs on cron, lands in your inbox every Monday morning. Best for: in-house teams that need market context, not just internal numbers.

📚 Internal marketing wiki with live metrics Stack: Porter MCP + Airtable MCP (or Notion MCP) Use Airtable or Notion as the schema, Porter as the data source. Claude Code keeps every page populated with current engagement rate, reach, and follower growth for every account — no stale screenshots, no copy-paste from Excel. New hires read one wiki entry and have full context on a client’s account. Best for: agencies and ops teams onboarding analysts or rotating account managers frequently.

🔔 24/7 alerts on engagement drops, reach declines, and follower loss Stack: Porter MCP + Slack MCP (or Gmail MCP) A Claude Code routine on cron pulls Instagram via Porter, evaluates thresholds — engagement rate drops below 2%, daily follower loss exceeds 5%, reach spikes 2× the trailing average — and pushes Slack or Gmail alerts the moment something crosses the line. You stop checking dashboards reactively; the dashboard checks itself and tells you when to look. Best for: any team that’s ever discovered a problem 48 hours too late because nobody opened the report.

Bottom line: Claude is for quick questions and ad-hoc dashboards. Claude Code is for building apps, live dashboards, alerts, and actual tools — anything you want to run on its own without re-asking. Same Porter MCP URL works in both, so you don’t pick once and lock in.

Use cases — what you can actually do once Instagram is connected to Claude

Getting the connection right is half the battle. The real value shows up in what you do next. Here are the use cases Porter users build around their Instagram data — from simple Q&A to full client-facing workflows.

1. Chat and ask questions directly

The simplest use case — and still the one 80% of marketers start with. Open Claude, ask a question, get an answer grounded in live data.

It’s the fastest way to replace a daily Instagram Insights check-in. But chat is table stakes — the interesting use cases come next.

2. Blend Instagram with your marketing data (Meta Ads, Shopify, HubSpot)

This is where a 360° view gets real. When you connect Instagram and your partner data (Meta Ads for paid social amplification, Shopify for e-commerce conversions, HubSpot CRM for lead nurturing), Claude can map posts, Stories, and Reels to actual purchases, sign-ups, or lead captures — using post URLs, campaign names, and publish timestamps — and give you attribution that no platform-side number can.

Claude handles the post URLs, campaign names, and publish timestamps mapping and joins. You get a client-ready attribution report that no single platform can generate on its own.

3. Automated alerts and notifications on Slack or Gmail

With Claude Code you can turn Instagram monitoring into a routine that runs on its own. Hook Porter’s MCP (for the data) together with a Slack or Gmail MCP (for delivery), then write a Claude Code scheduled task that pulls performance every morning and pings you only when something actually needs attention.

No dashboards, no daily check-ins. The report comes to you — and only when it matters.

4. Client-ready presentations with live data (Gamma, HTML, PDF)

A common agency pain: you send clients a Instagram Insights link, native analytics break, the client panics — and you spend an hour explaining a broken dashboard. With Claude you can build the presentation itself — as a Gamma deck, a custom HTML page, or a PDF — populated with live numbers each time.

The presentation becomes a delivery artifact you send to the client, not a dashboard that depends on another tool staying up. No broken iframe, no login prompts, just the content.

Instagram fields and metrics you can query with Claude

Before you start writing prompts, it helps to know what data is actually available. Porter MCP gives Claude access to 104 Instagram fields and metrics across posts, Stories, Reels, and audience dimensions, plus breakdowns by date, post type, media product type, and audience demographics. And the same MCP URL also unlocks 25+ other sources — so Claude can blend Instagram with Google Ads, GA4, Shopify, HubSpot and more in a single prompt.

Dimension

Account nameAccount IDAccount IG IDAccount picture URLUsernameTaps on text message linkFollowers city (metric)Followers city

Metric

Account pictureTaps on email linkProfile new followersTaps on directions linkProfile impressionsTaps on phone linkProfile viewsProfile reach

Prompts you can copy-paste today

1. For agencies {#prompts-agencies}

Use these when you’re managing multiple client accounts and need fast, standardized reporting.

2. For brand teams {#prompts-brand-teams}

Use these when you’re optimizing content strategy, posting schedules, and brand voice consistency.

3. For creators & DTC {#prompts-creators-dtc}

Use these when you’re a creator or direct-to-consumer founder posting daily and need rapid gut-checks on what’s working.

4. Cross-channel {#prompts-cross-channel}

Use these when you want to blend Instagram with other platforms for unified social reporting.

How to use Claude Code for Instagram without getting banned

This is the message that terrifies every social media manager who has tried to scale Instagram operations through unofficial automation. The thread documents how a marketing team lost access to a business account with 50K+ followers after using third-party scraping tools that violated Meta’s Terms of Service. The real cost isn’t just the ban — it’s the lost audience, the broken client campaigns, and the weeks-long appeal process through Meta’s opaque support system. For marketers connecting Instagram to Claude, the lesson is stark: the API path you choose determines whether you’re building on sand or bedrock.

Meta’s enforcement is quota-based and pattern-based, not tool-based. Instagram doesn’t ban accounts because you used Claude or an MCP. It bans because of how the data was accessed: unauthorized scraping, exceeding rate limits, or using unapproved third-party automation tools that mimic human behavior. Read-only access through the official Instagram Graph API with proper OAuth permissions is safe. Write-at-scale, browser automation, parallel API bursts, and “public data” scraping are not. Meta’s systems detect abnormal request patterns — including velocity, IP clustering, and behavioral signatures — and respond with throttling first, then temporary restrictions, and finally permanent account suspension for repeated violations.

The two behaviors that actually get accounts banned {#risky-behaviors}

After reviewing official docs and community threads, two patterns come up again and again.

1. Unauthorized scraping and “public data” extraction. Using unofficial tools or browser automation to scrape Instagram profiles, posts, or follower lists without the Graph API violates Meta’s Platform Terms. This triggers automated detection because the request patterns don’t match legitimate API signatures. The consequence ranges from IP blacklisting to permanent account suspension. What to do instead: Use only the official Instagram Graph API with a registered Meta App and approved permissions.

2. Exceeding rate limits with bursty traffic. The Instagram Graph API enforces rate limits of approximately 200 calls per user per hour. Bursting 50 requests in 10 seconds to “refresh all metrics” triggers throttling. Meta’s BUC (Business Use Case) rate limiting model allocates quota per-app, per-account, and per-user. When you exceed it, the API returns error code 4 (application-level limit), 17 (user-level limit), or 32 (page-level limit). What to do instead: Batch requests, implement exponential backoff, and stay under 80% of your allocated quota.

3. Attempting DM automation or comment botting without approved permissions. The Instagram Messaging API requires Meta app review and Business Account verification. Many third-party tools claim “DM automation” but operate outside approved channels, using unofficial methods that Meta detects as automated behavior. The Reddit thread: modded Instagram warning documents accounts receiving warnings after using such tools. What to do instead: Only use DM features through officially approved Meta Business Partners, or avoid DM automation entirely and focus on Insights and analytics use cases.

Both behaviors trigger Meta’s automated detection systems. If you want to use Claude for Instagram safely, stick to read-only Graph API access through properly authenticated official channels.

The 5-rule safety protocol {#safety-protocol}

Based on Instagram’s documented rate limits and policies and the behaviors that have actually caused account bans — not guesswork:

• Use only official Instagram Graph API endpoints. The official API requires a Business or Creator account, a registered Meta App, and OAuth authentication. Unofficial scraping tools violate Meta’s Platform Terms and expose accounts to permanent suspension. Porter MCP uses only official Graph API endpoints with proper OAuth flows.

• Respect the 200 calls per user per hour rate limit. Multiple community sources (Stack Overflow, WP Social Ninja, CreatorFlow) cite 200 API calls per user per hour as the Instagram Graph API threshold. Exceeding this triggers error code 4, 17, or 32 and temporary throttling. Porter MCP implements server-side request batching and caching to stay well under this limit.

• Never attempt to automate DMs or comments without Meta approval. Instagram Messaging API access requires app review and Business Account verification. Unauthorized DM automation is one of the fastest paths to an “automated behavior” ban. Porter MCP does not offer DM automation — it focuses on read-only analytics and reporting.

• Implement exponential backoff on rate limit errors. When you receive error code 4, 17, or 32, wait before retrying. Immediate retries compound the throttling. Porter MCP handles this automatically with built-in backoff logic.

• Cache Insights data proactively — Stories expire in 24 hours. Instagram Stories data is only available through the Insights API during the 24-hour active window. After expiration, historical Story metrics (exits, taps, reach) are lost unless collected in real-time. Porter MCP’s scheduled sync ensures Story data is captured before it disappears.

What Porter MCP does differently: it enforces these safeguards at the platform level. Porter uses read-only Graph API endpoints by default — no write operations that could trigger automated behavior detection. Rate limiting is handled server-side with intelligent request batching, staying well under the 200 calls/hour threshold. OAuth scopes are minimized to only what’s needed for analytics (Insights, Business Discovery), not messaging or posting. Per-account request quotas are tracked and throttled automatically. That’s the behavior Meta’s automated systems reward: predictable, low-velocity, read-only API usage through properly authenticated official channels.

Frequently asked questions

An Instagram MCP (Model Context Protocol) is an open standard that lets AI tools — Claude, Claude Code, ChatGPT, Cursor — connect to your Instagram data without custom integrations. Porter’s MCP server makes your posts, Stories, Reels, and audience insights available through one URL: no tokens, no scripts, no developer setup.

Claude is the conversational product (web, app, mobile). Claude Code is a terminal-based developer tool that can write scripts, save files, and automate workflows. Both can connect to Instagram via MCP.

Meta’s API refreshes approximately every few minutes to 24 hours depending on the metric. Porter MCP pulls live, so your data is always within that window.

Yes. Meta enforces roughly 200 API calls per user per hour. Porter MCP batches and caches requests automatically so you rarely hit them.

Two common reasons: (1) Processing delays — API data can lag behind the native UI by minutes to hours. (2) Attribution windows — Meta applies different attribution models in Insights versus the Graph API. The fix: compare the same date range and metric definition in both places.

Only if you use it badly. Meta’s enforcement is behavior-based: unauthorized scraping and exceeding rate limits trigger bans. Following the 5-rule safety protocol above puts you in the same risk bucket as approved analytics tools like Hootsuite or Sprout Social.