Give it a folder.
Point Margins at one folder on your computer. Your Obsidian vault, a project directory, anything. Claude only ever sees what’s inside that folder. Nothing else on your machine.
Margins makes Claude smarter by turning your messy files into usable context. Drop in notes, transcripts, PDFs. Claude searches across them, cites sources, and compiles raw input into clean structured pages. Runs locally. No servers, no API key.
How it works
You decide what Claude can see, you decide what Claude writes, you ask later.
Point Margins at one folder on your computer. Your Obsidian vault, a project directory, anything. Claude only ever sees what’s inside that folder. Nothing else on your machine.
Drag in notes, writing, PDFs, meeting transcripts, anything you want Claude to know about. Ask Claude to compile it. Margins stages a clean source page in proposed/ for you to accept.
Claude searches the sources you’ve built, cites where each fact came from, and surfaces connections you didn’t make: a meeting that overlaps with another, a thread you forgot was open, a pattern across months of notes. New edits go in proposed/ for your review.
Want the longer version? See the full walkthrough — folder layouts, the connection diagram, every tool Claude can call, and what the first month looks like.
Use cases
Seven scenarios across notes, transcripts, PDFs, code, decisions. Same move every time: Claude pulls the context, follows the thread, and finds what you'd miss.
UserCoffee with Casey Tran tomorrow at 9am. We met at the conference back in March. Brief me — I don't remember much. Use margins.
ClaudeLoaded tools, used Margins — margins_start, search_vault for "Casey Tran" (5 matches), get_backlinks for casey-tran (7 pages link back).
ClaudeThree direct touch points. Pulling the entity page, the conference notes, and the follow-up on LinkedIn — wiki/entities/casey-tran.md, raw/2026-03-15-conference-dinner.md, raw/2026-04-22-casey-linkedin.md.
ClaudeCasey runs platform partnerships at Lumen. Her current obsession is agentic workflows for sales teams. Checking whether anything else in the vault touches that — search_vault for "agentic workflows" surfaces an article you clipped in April and a coffee with Sam on April 22 where he called Lumen "the one to watch in agentic sales tooling."
ClaudeCasey Tran — coffee tomorrow, 9am. Platform partnerships at Lumen, ex-Stripe, intro'd by Jordan at the March conference dinner. Current focus: agentic workflows for sales teams.
Where you left it. You owe her your post on vendor consolidation (never sent). She offered an intro to her old Stripe colleague at Plaid; you said you'd come back with a clearer ask.
Why she's circling back. Her April LinkedIn message says her team is "rethinking surface area" and asked what you've been seeing on the seller side. Probably evaluating you as a partner.
Connections worth surfacing. The Information piece you clipped on April 10 is a long read on agentic workflows for B2B sales — Casey's exact territory. Reference it directly. And Sam, on April 22 (raw/2026-04-22-coffee-sam.md), called Lumen "the one to watch" without knowing you'd already met her.
Posture. Lead with the post you owe — apologize fast and move on. Ask about the surface-area reset. Hold the Plaid intro back unless she opens it.
Compare
There are a few other ways to point an AI at your notes. Here's where they overlap with Margins and where Margins is more specific.
FAQ
Margins MCP is a local-first MCP server. It gives Claude Desktop and Claude Code a small set of tools: search your files, read individual pages by path, follow wikilinks and backlinks, and stage write proposals to a proposed/ folder you review before accepting. The tools run on your machine against a folder you point them at.
No. Margins uses your existing Claude Pro or Max subscription. There are no per-token costs and no separate API account. If you already pay Anthropic, you don't pay anything else to use Margins.
Yes. The installer writes the MCP config for both. It does not work with the claude.ai web interface yet; the browser version doesn't support MCP connectors.
Claude can only see the one folder you point Margins at. Not your Documents, not your Desktop, not your whole machine. Just that folder. If you don't drop a file into it, Claude doesn't know it exists.
Your files stay on your disk. Margins runs locally; no content is sent to any server controlled by Margins. The only data leaving your computer is whatever Claude needs to answer your prompt, which goes directly from your machine to Anthropic under your existing subscription. Margins is not a hosted service.
Any folder with Markdown, plain text, or PDFs in it. Margins doesn't care if it's a notes app's vault, an iCloud Drive folder, a project repo, or a directory of meeting transcripts. Obsidian works particularly well because Margins understands wikilinks and backlinks, but it isn't required.
If you point Margins at a folder that doesn't have a structure yet, the installer can scaffold a starter: raw/ for inputs, proposed/ for staged writes, and a CLAUDE.md operator manual.
No. Claude can only propose writes. Every proposed edit is staged in a proposed/ folder inside your vault. You review the file, then move it into place to accept (or delete it to reject). Your real notes are never modified without your action.
Filesystem MCP gives Claude raw file access to any folder, with no review step. Margins is vault-aware: it understands wikilinks and backlinks, has a propose-then-accept safety model, includes tools that compile raw transcripts into structured source pages, and exposes vault context on first use so Claude knows what it's looking at.
Filesystem MCP is more general; Margins is more specific to how knowledge-work vaults are actually shaped.
Yes, MIT-licensed. The source is on GitHub and the npm package is margins-mcp. Margins itself is free. The only ongoing cost is your existing Claude subscription, which you would have anyway.
Get started
You saw it. Now run it on your files.
Double-click. Pick a folder. Ask Claude.
Margins shows up in your Connector list with its logo.
The installer writes configs for Claude Desktop and Claude Code, scaffolds raw/, proposed/, and .margins in your folder, and verifies. To update later: margins-mcp install --update.
Margins can scaffold a starter for you. wiki/, raw/, proposed/, plus a CLAUDE.md operator manual.
Done. Now install the connector (the .mcpb download above) and point it at the Margins/ folder you just created.