How to Let Claude Search and Read Your Local Files on Windows (Step-by-Step MCP Setup)

2026-11-13·7 min read
Quick Answer: LocalSynapse is a free desktop app for Windows and macOS that indexes the documents on your PC and includes an MCP server, so Claude can search and read them. On Windows: install LocalSynapse, let it index your folders, open its MCP page, press Connect next to Claude Desktop, then restart Claude Desktop. That adds a 'localsynapse' entry to %APPDATA%\Claude\claude_desktop_config.json which starts LocalSynapse.exe with the argument mcp. For Claude Code, the same page shows a ready-made 'claude mcp add' command to copy. Claude then gets nine tools, including search_files and get_file_content. Indexing stays on your PC, but the passages Claude reads become part of your conversation with Anthropic.

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?

How do I connect Claude Desktop to my local files?

  1. 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.
  2. 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.
  3. Open the MCP page and press Connect in the Claude Desktop section. LocalSynapse writes a localsynapse entry into %APPDATA%\Claude\claude_desktop_config.json. Any other MCP servers already in that file stay as they are.
  4. Restart Claude Desktop. The app tells you this too: the new server is picked up when Claude Desktop starts.
  5. Check that it works. Ask Claude: "Use LocalSynapse to check the indexing status." It should call get_pipeline_status and 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:

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

What LocalSynapse does not do


Related Posts

Try LocalSynapse Free

Search inside files, works offline, free

Go to Home

Related Posts