The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Pil listing page.
Get started · How it works · Other AI tools · What's inside
mcp-name: io.github.pjpoulose/pil
Get PIL in 3 steps
1. Copy-paste this into Muse:
2. When it asks, link your Instagram (one tap in your browser).
3. Download the app file it sends you → unzip → double-click Start PIL → click Install.
That's the whole thing. Your Muse does the setup, the reading, and the building. Want it on your phone too? Just ask your Muse — it handles that as well.
Prefer to do it yourself? One command sets everything up.
- Mac / Linux:
curl -fsSL https://raw.githubusercontent.com/pjpoulose/PIL/master/bootstrap.sh | bash- Windows (PowerShell):
irm https://raw.githubusercontent.com/pjpoulose/PIL/master/bootstrap.ps1 | iexThen build your library with the commands in Manual setup.
Every day you save posts you'll never find again. PIL (Personal Instagram Library) turns your Instagram saved collection into a private knowledge base on your own machine: every post deep-read by vision AI — narrative summaries, key points, how-to steps, links it discusses, automatic tags — searchable in seconds and queryable live from your AI coding tools.
Code is shared, data stays home. This repo contains only code, the database schema, config examples, and docs. Your saved posts, captions, and account details never leave your computer — ingestion, extraction, search, and the MCP server all run locally. A
.gitignoreblocks databases, configs, and exports from ever being committed.

Concept mockup with sample data — your library looks like this, with your posts.
Connect the read-only MCP server and your other AI tools can query your library live — always current, nothing to re-upload. Your Muse can wire it up for you. How to connect →
Prerequisites: python3 (3.11+) and instagram-cli with your Instagram
account linked (run instagram-cli accounts — it must list your account).
The one-line installer at the top of this page handles all of this for you.
Build your library (each step is resume-safe — re-run any time):
Ask it anything — via the live MCP server or the static export:
That's it. Re-run ingest_saved.py whenever you save new posts; extract_content.py
only processes posts it hasn't seen yet.
The app: ask your Muse to build and send it — see Your library as an app.
| Instagram saved tab | PIL | |
|---|---|---|
| Find a post from 2 years ago | Scroll endlessly | Full-text search in seconds |
| Remember what a post actually said | Rewatch / reread it | AI summary, key points, how-to |
| Links a post mentioned | Gone unless you saved them | Extracted and clickable |
| Use it inside your AI tools | Screenshots and retyping | MCP server or JSON export |
| Where your data lives | Meta's servers | Your machine, SQLite |
Live (recommended): MCP. Point any MCP-compatible assistant at the read-only server and every question reads your current database — always up to date, no exports, no re-uploads:
Wiring for Claude Code, Claude Desktop, and Cursor: references/mcp_clients.md. Any MCP-compatible client works — and your Muse can connect it for you if you'd rather not touch configs. Available tools:
| Tool | What it does |
|---|---|
search_posts | Text search over captions + deep-read knowledge, with optional folder/tag filters |
get_post | Full record for one post: summary, key points, how-to, links, folders, tags |
list_folders | Your saved collections with indexed counts |
list_tags | Tags by usage |
library_stats | Totals + deep-read coverage per field |
The server opens the database with SQLite mode=ro and exposes SELECT-only
tools — it cannot modify your library. (Attack-tested: SQL injection, write
attempts, and limit abuse all verified blocked.)
Snapshot: file upload. Ask your Muse to send you the web_data.json file
(built with export_web.py): every post with its deep-read knowledge in one
file. Attach it to any AI chat (Claude, ChatGPT, …) and ask questions like any
document. It's frozen at export time — a snapshot, not a live connection — so
ask your Muse for a fresh copy after you save new posts.
Directly (advanced). The database is plain SQLite at <data_dir>/pil.sqlite
(schema in schema.sql). Open it read-only with any SQLite tool.
These files hold your personal Instagram data — keep them on your own machine and only share them with tools you trust.
Your Muse builds the app for you and sends it to you — for your computer and your phone. Just ask:
No commands, no hosting setup, no terminal — your Muse takes care of all of it.
Prefer exploring over querying? The Signal Deck (dashboard/) builds a
self-contained HTML dashboard from your local PIL database: a topic-ring hero
over everything you saved, search → synthesis (The Brief), a sources rail, a
sticky index, and a full archive grid. One file, works offline, your data
never leaves your machine.
See dashboard/README.md for details, PWA notes, and the QA suite.
Do I need to know how to code? No. Copy-paste the prompt at the top of this page into Muse — it does everything with you. The only things you'll do yourself are linking Instagram (one tap in your browser) and downloading the app file it sends you.
Where does my Instagram data go? Nowhere. Code is shared, data stays home: your saved posts, captions, and account details never leave your computer. Nothing is uploaded to us — there is no "us"; there's no server, no account, no cloud.
Does it cost anything? PIL is free and open-source (MIT). There is no subscription and no account to create. The AI deep-read step runs through your own Instagram/AI setup.
Does the app work offline? Yes. Once installed, the desktop and phone apps run fully offline — search, rooms, tags, and answers all work without internet.
Which phones and computers? Windows, Mac, and Linux for the desktop app; iPhone and Android for the phone app. On Android, tap Install app in Chrome; on iPhone, use Safari's Share → Add to Home Screen.
I saved new posts — how do I add them? Just tell your Muse "I saved new posts." It fetches and deep-reads only the new ones, then refreshes your app and files.
Can I share my library with someone? Your library is files on your machine — you can copy them to someone else's computer, but they contain your personal Instagram data. Treat them like anything private: don't publish or upload them anywhere public.
Something failed — what now?
Tell your Muse what you saw — it can diagnose and fix it directly. (Running
the manual setup below? Re-run the installer — it's safe to run any number of
times — and check python3 --version is 3.11+.)
Something wrong? Tell your Muse what happened — it can diagnose and fix most issues itself.
Running the manual setup yourself?
PIL account_id is not configured → copy the example config and set
account_id to your user_fbid from instagram-cli accounts.429 rate limits are handled with backoff inside the scripts.mcp<2 in the Python that runs it (2.x renamed the API).PRs and issues welcome — better extraction prompts, new query clients, new export formats. Fork it, ship it, make it yours. If it saved you from the endless scroll, a star helps others find it.
MIT. Built by Paul Poulose.