Skip to main content

instagram-data-mcp (local stdio package)

A small local MCP server for public Instagram data, published on PyPI as instagram-data-mcp. It gives Claude, Cursor and any other MCP client 27 read-only tools: profiles, posts, reels, stories, highlights, comments, likers, followers, hashtags, places, audio and search.

Most people don't need this package. The same tools are available from the remote server at https://data.fastsocial.co/mcp, with sign-in in the browser and nothing to install. Setup for that is in FastSocialCo/instagram-data-mcp. Use this package if your client only runs local (stdio) servers.

Run it

Get a key at https://fastsocial.co/instagram-api (there is a free plan), then:

{
  "mcpServers": {
    "instagram-data": {
      "command": "uvx",
      "args": ["instagram-data-mcp"],
      "env": { "IG_DATA_API_KEY": "your_key" }
    }
  }
}

No uvx? pip install instagram-data-mcp and use "command": "instagram-data-mcp" instead.

What it does and what it sends

The whole server is server.py, about 150 lines. It reads the bundled openapi.json (the public spec of the Instagram Data API) and turns each GET endpoint into one tool.

When a tool is called, it makes one HTTPS GET request to https://data.fastsocial.co/v1/<endpoint> with the tool's arguments as query parameters, your key in the X-API-Key header and instagram-data-mcp as the user agent. It returns the JSON response as is. That is the only network request it makes.

  • Every tool reads. Each one is marked readOnlyHint: true. None can log in to Instagram, post, follow, like or message.
  • It writes no files and stores nothing. Your key stays in your client's config and is only ever sent in that header.
  • No install scripts, no telemetry.

Privacy policy: https://fastsocial.co/privacy · Terms: https://fastsocial.co/terms

Settings

Env var Default
IG_DATA_API_KEY none Required
IG_DATA_API_BASE https://data.fastsocial.co
IG_DATA_API_TIMEOUT 60 Seconds

Tools

The tool list and what each one costs in credits are in the plugin README and the API docs.

Security

Report a vulnerability to contact@fastsocial.co. See SECURITY.md.

License

MIT

Metadata

Release files for instagram-data-mcp 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for instagram-data-mcp 0.1.5
File Size Uploaded
instagram_data_mcp-0.1.5.tar.gz 11.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for instagram-data-mcp 0.1.5
File Interpreter ABI Platform
instagram_data_mcp-0.1.5-py3-none-any.whl Python 3 none any Details

Total release size: 24.8 kB

Release files / instagram_data_mcp-0.1.5.tar.gz

Download URL instagram_data_mcp-0.1.5.tar.gz
Size 11.8 kB
Tags Source
SHA-256 checksum
How to use checksums
1b4c920e58feba6b40bdaa5ea4b195afa249f898016fb7d6c1b9d8e7b3b4254a
BLAKE2b-256 checksum
How to use checksums
e44fa4e7f796f90ec089720964b56b607227efb775faae23710138da3b30f433
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release files / instagram_data_mcp-0.1.5-py3-none-any.whl

Download URL instagram_data_mcp-0.1.5-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
56baadda8200c349c825f21b3115299f06d2f8365c066e2de987b029ef9746da
BLAKE2b-256 checksum
How to use checksums
c88ba3b36a7090e519f9e63df6daf3bf397f6f1806b575926a8d6b39d9536348
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.7

2 release files

0.1.6

2 release files

This release

0.1.5 This release

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page