Which tool you need
To give file access there's only one right server: the filesystem one (@modelcontextprotocol/server-filesystem), the most widely used and officially maintained. On the AI side you need an assistant that supports MCP: Claude in the desktop apps or a compatible code editor. The part that changes is the format of the configuration file depending on the app; the server is the same.
How to do it
The principle doesn't change between assistants: you declare the server, give it the folder, restart.
- Choose the folder. The one that contains the files you want to work on. A specific folder, not the whole drive.
- Add the server to the configuration file. The working syntax:
{
"mcpServers": {
"file": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/yourname/Documents/work"]
}
}
}
The last value is the accessible folder. Replace it with the real path of yours (on Windows it looks like C:\\Users\\name\\Documents\\work, with double backslashes).
- Restart the assistant completely, so it re-reads the configuration.
- Put the AI to work on the files. Now you can ask concrete things. For example: "read all the documents in the folder and give me a list of what they contain", or "find the file where I wrote the quote for client Rossi and summarize it for me".
A concrete example
Chiara has dozens of meeting minutes scattered across a folder and never remembers where anything is. She connects the filesystem server to that folder in Claude Desktop's configuration file, changes the path and restarts. Then she asks: "search across all the minutes for where we decided the marketing budget and tell me the amount and the date".
Claude opens the files on its own, finds the right minutes and answers with the amount and when it was decided. Before, Chiara would have opened the documents one by one searching from memory. Now the AI acts as a search engine over her own files, and she asks questions in plain language instead of digging through folders.
When it does NOT work (and how to fix it)
If the AI doesn't see a file you just added
Sometimes a file placed in the folder after startup doesn't show up right away. Ask the AI to "re-read the contents of the folder": that's usually enough. If it still can't find it, restart the assistant, so the server restarts and re-reads everything.
If there are too many files or they're too heavy
If the folder contains hundreds of documents or huge files, the AI may slow down or fail to read them all at once. Point the server at a narrower subfolder with only what you need right now, or ask the AI to work on one file at a time by naming it.
If the AI can't read the content
Files that are images or scans (a photographed PDF) have no readable text. First run that file through a free OCR (Optical Character Recognition, recognizing text inside images) service like iLovePDF or Adobe, which turns it into text, and put it back in the folder.
A tip from someone who actually uses it
Create a dedicated folder — call it "AI" or similar — and put in it only the files you want the assistant to work on. You connect the server to that one and that's it. This way you never give access to everything, you always know what the AI can see, and when a job is done you move the files out. It's tidier and much safer than pointing the server at your entire documents folder.
Frequently asked questions
Can the AI also modify or create files, not just read them?
The official filesystem server allows both reading and modifying the folders you specify. Serious assistants, however, ask for your go-ahead before changing or deleting anything. If you want the AI to be able to only read, see the guide on how to limit access to read-only.
Are my files uploaded to the internet?
The server runs on your computer and reads the files locally, but the AI assistant processes the requests on its own servers: the content you have it read still passes through the model. For confidential documents, weigh up what you feed it and prefer an assistant with solid privacy guarantees.
Do I have to keep the assistant always open for it to work?
Yes: the filesystem server starts together with the assistant and lives as long as the app is open. When you close the assistant, the connection breaks and your files become unreachable again, which is also a small extra safeguard.