How do I connect Instagram to Claude Code without writing code?

Add a Meta/Instagram MCP server with a single command: claude mcp add --transport stdio --env META_ACCESS_TOKEN=your_token meta -- npx -y @oliverames/meta-mcp-server. Then run /mcp inside Claude Code to authenticate. The MCP exposes ready-made tools, so you never touch the raw Graph API.

What is the first call I should make after connecting the Meta MCP?

Always meta_list_pages first. It caches the Page-level tokens that every other call depends on. If you skip it, later calls fail because they don't have the Page context they need.

Connect the Meta MCP

Q: Are MCP servers safe to install?

Only install servers you trust. An MCP server that fetches external content (like captions or comments) can expose you to prompt-injection risk — malicious text in fetched content trying to steer the agent. Verify the source and prefer well-maintained, open servers.

You have the token from the last lesson. Now you plug it into Claude Code. There are two ways to do this — the fast one (a ready-made MCP server) and the build-it-yourself one (next lesson). Start here; it's one command.

An MCP server is a small program that gives Claude Code a set of tools — in this case, tools that talk to the Meta Graph API for you. You don't write the API calls; you install the server and ask in plain English.

Option A: add the server in one command

Paste this into your terminal, swapping in the token you created:

claude mcp add --transport stdio --env META_ACCESS_TOKEN=tu_token meta -- npx -y @oliverames/meta-mcp-server

That registers a server called meta and hands it your token through an environment variable (so it never gets hardcoded into a file). The npx -y part means you don't install anything globally — it fetches and runs the server on demand.

Then, inside Claude Code, authenticate:

/mcp

/mcp lists your connected servers and lets you confirm auth. Once meta shows up connected, Claude Code can call its tools.

The one rule: `meta_list_pages` first

There's a gotcha that eats a lot of people's first hour:

Warning:

Your first call is always meta_list_pages. It caches the Page-level tokens that every other call depends on. Skip it and the next calls fail with confusing errors, because they have no Page context to work from.

So your first prompt after connecting is simply: "Call meta_list_pages." After that, ask for your reels, your insights, whatever — the plumbing is warm.

Alternatives if that server doesn't fit

@oliverames/meta-mcp-server is the quickest starting point, but MCP servers come and go. If it's unmaintained or missing a tool you need, swap it:

mcpware/instagram-mcp — 23 tools, Instagram-focused.
mikusnuz/meta-mcp — 57 tools, built on Graph API v25.0.
pipeboard-co/meta-ads-mcp — reach for this one if you also run paid ads and want ad data alongside organic.

They all install the same way — swap the package name after npx -y.

The trust caveat

An MCP server runs with your token and can fetch content. That's power, and power cuts both ways.

Warning:

Verify you trust each server before you install it. Servers that fetch external content can expose you to prompt-injection risk — malicious text hidden in a caption or comment trying to hijack the agent. Prefer open, well-maintained servers, and read what a server does before handing it your token.

If a server's provenance makes you uneasy, that's your cue to take Option B in the next lesson and build the puller yourself — same result, code you control.

Knowledge check

What must your first call to the Meta MCP always be?

Key takeaway

The no-code path is one command — claude mcp add ... npx -y @oliverames/meta-mcp-server — then /mcp to authenticate. Always call meta_list_pages first to warm the Page tokens. Only install servers you trust, since content-fetching servers carry prompt-injection risk.