How to Let Claude Search and Read Your Local Files on Windows (Step-by-Step MCP Setup)
Claude can't see the files on your computer by default. Ask Claude Desktop to find last quarter's pricing workbook and it has nothing to search. The Model Context Protocol (MCP) closes that gap: Claude calls tools that run on your own PC, and those tools do the searching. This guide sets that up on Windows, step by step, with LocalSynapse as the local server.
What do you need?
- Windows 10 or 11 (64-bit). LocalSynapse also runs on macOS; the paths below are for Windows.
- Claude Desktop, Claude Code, or another MCP client that can start a local server.
- LocalSynapse — free, no account or login.
How do I connect Claude Desktop to my local files?
- Install LocalSynapse. The installer sets it up for your Windows user, by default at
%LOCALAPPDATA%\Programs\LocalSynapse\LocalSynapse.exe. The Windows build is not code-signed, so Microsoft Defender SmartScreen may warn you; choose More info, then Run anyway. - Let it index your folders. LocalSynapse reads Word (.docx), Excel (.xlsx), PowerPoint (.pptx), PDF, HWP/HWPX, OpenDocument, RTF, HTML, email (.eml, .msg) and plain-text files. Keyword search works without extra downloads. Search by meaning needs the optional AI model (about 2.3 GB), which the app downloads only if you choose to install it.
- Open the MCP page and press Connect in the Claude Desktop section. LocalSynapse writes a
localsynapseentry into%APPDATA%\Claude\claude_desktop_config.json. Any other MCP servers already in that file stay as they are. - Restart Claude Desktop. The app tells you this too: the new server is picked up when Claude Desktop starts.
- Check that it works. Ask Claude: "Use LocalSynapse to check the indexing status." It should call
get_pipeline_statusand report how far extraction and embedding have got.
What does the Connect button write?
This is the whole entry. The command is the path of the LocalSynapse you are running, and the MCP page shows that exact path, so you can also add it by hand:
{
"mcpServers": {
"localsynapse": {
"command": "C:\\Users\\YOUR_NAME\\AppData\\Local\\Programs\\LocalSynapse\\LocalSynapse.exe",
"args": ["mcp"]
}
}
}
How do I add it to Claude Code?
The same MCP page shows a command for Claude Code with a copy button. It has the form claude mcp add localsynapse -- "<path to LocalSynapse.exe>" mcp, already filled in with your path. Paste it into a terminal. The page also shows claude mcp remove localsynapse for undoing it.
What about Cursor, Cline and other MCP clients?
Any client that can launch a local (stdio) MCP server works the same way: the command is LocalSynapse.exe and the only argument is mcp. The client starts LocalSynapse in the background when it needs it, so the LocalSynapse window does not have to stay open. The MCP integration page has the general reference, and this Hermes Agent guide shows another client's config.
What can Claude do once it's connected?
Claude gets nine tools:
search_files— searches what is written inside your documents (keyword search combined with semantic search) and returns the matching passages with their position in each document.get_file_content— reads the extracted text of up to 20 indexed files in one call.list_indexed_files— lists what is indexed, filtered by folder, extension or extraction status.get_pipeline_status— indexing progress.get_spreadsheet— an .xlsx workbook as cells, types and merged ranges (details).get_email_thread— the parents and replies of an indexed email, oldest first.get_timelineandget_work_session— file changes and email arrivals in a period, or around one file or moment.preview_index_removal— a read-only preview of what an index cleanup would select.
A typical exchange: you ask "What did the vendor contract say about termination notice?" Claude runs search_files, gets the passage from the contract PDF, and answers with the file it came from.
Troubleshooting
- Claude doesn't list the tools. Restart Claude Desktop after connecting, and check that the config file above contains the
localsynapseentry. - The MCP page says "Not connected" although you registered before. The page counts an entry as connected only if it points to the copy of LocalSynapse you are running now. Press Connect again to update it.
- Searches come back empty. Ask Claude to run
get_pipeline_status; indexing may not have reached those files yet. Files that exist only in the cloud (for example OneDrive "online-only" files) are skipped — see why and how to fix it.
What LocalSynapse does not do
- It doesn't keep tool results private from your assistant's provider. Files are not uploaded, but whatever Claude reads through a tool becomes part of the conversation. See what stays local and what doesn't and the privacy page.
- It skips cloud-only placeholder files rather than downloading them.
- No OCR. Scanned PDFs without a text layer have nothing to index.
- Legacy .doc, .xls and .ppt files are not content-indexed.
- Windows and macOS only. The Windows build is not code-signed and the macOS builds are not signed by Apple.
- It runs on the CPU. No GPU is needed or used.