Can Claude Desktop Access Local Files? Setup and Limits
Claude Desktop can read files you upload into a conversation and can access folders you connect through an MCP filesystem server. Here is how each method works, what it can read, and what it cannot.
Updated 5 min read
Claude Desktop can read files you upload into the conversation and can access local folders through an MCP filesystem server, which you configure separately. Tools like fenbs give you a place to keep the project context, source file links, and decisions that should survive beyond a single session, without requiring disk access for everything.
The two methods serve different needs. File uploads are quick for a one-off document. An MCP filesystem connection is better when you want Claude to browse a folder or read multiple files without manual uploads each time.
File uploads: reading a document in the current chat
Drag a file into Claude Desktop or use the attachment button to upload it. Claude can read PDFs, text files, code files, Markdown documents, and common document formats. The file is available for the current conversation only. When you start a new chat, Claude does not have that file.
This is enough for most one-off tasks: summarizing a report, reviewing a contract, or checking a piece of code. It does not give Claude access to any other files on your machine, and nothing from your drive is read without your upload.
For large files, ask Claude to quote from a section near the end of the document to confirm it processed the full file. If it cannot, the file may have been truncated.
Connecting a folder through MCP
MCP (Model Context Protocol) is a standard way for AI apps to connect to outside tools. Claude Desktop supports MCP servers, and there are filesystem servers that let Claude read a folder you specify. You add the server to your Claude Desktop MCP configuration file and restart the app.
Once connected, you can ask Claude to list files in the folder, read a specific file by name, or search for text across files. Claude acts within the directory you gave it access to and cannot read files outside that path. See Claude Desktop MCP config for the step-by-step configuration.
When Claude accesses files through MCP, it cannot reach anything outside the folder path you configured. System files, other user directories, and cloud storage mounted at a different path are all out of scope. If you need Claude to work with a second folder, add a second path to the MCP configuration. This bounded access is what makes the MCP approach safer than granting broad disk permissions.
Full disk access: what it means on macOS
On macOS, some MCP filesystem servers prompt for Full Disk Access in System Settings. This permission lets an app read anywhere on your drive. Think carefully before granting it: it is broader than most tasks require and gives access to system files and personal folders you may not intend to share.
A safer approach is to configure the MCP server with a specific folder path and grant access only to that directory. This limits Claude to the files relevant to the current project without exposing your entire drive. Most development and writing workflows can be served by a project folder rather than the full disk.
What Claude Desktop cannot do with local files
Claude Desktop cannot write to files unless an MCP server with write access is configured for it. It cannot read files outside the scope you defined during setup. It also cannot sync with cloud storage automatically; for Google Drive or Dropbox access, you need a separate MCP server for that service.
If a filesystem MCP server is not behaving as expected, see Claude Desktop MCP not working for common troubleshooting steps. For Claude Code specifically, see Claude Code deleted files if Claude has taken unexpected write actions.
Keeping project context without full disk access
Many projects do not need Claude to read your entire drive. What they need is for Claude to know what the project is trying to achieve, which files matter, where they live, and what has already been decided about them. Keeping that context in a structured record outside the filesystem is often cleaner and more durable than giving Claude broad read access.
In fenbs, you can link to files, record the decisions made about them, and note where the work stands. The next session reads that record rather than scanning a folder. If a different AI app or a colleague takes over, they get the same structured starting point without needing access to your local drive.
Keep project context without broad file access
Add your project to fenbs with links to the key files, the decisions made about them, and where the work stands. Connect Claude Desktop over MCP from Integrations, and each session reads the current context at the start rather than relying on disk access to reconstruct it.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account. Your personal board is free and needs no credit card.
- Add a project. Write the goal and list the key files by name or link in the project description or a task.
- Record decisions about those files in Decisions and rules: which version is current, which sections need review, which format is approved.
- Connect Claude Desktop to fenbs over MCP from Integrations using the setup guide for Claude Code or Claude desktop.
- At the start of each session, ask Claude to read the project context. Ask it to save progress before you finish.
fenbs does not access your local files. It keeps the structured context that helps Claude use those files effectively without needing to scan your drive.