Local connections in the desktop app
The desktop app can start local MCP servers via stdio. This gives the AI access to extended Google and Microsoft features, Nextcloud, and other tools that a browser cannot run. Local file access is built-in and does not require an MCP server.
Onboarding
During the initial setup, you go through these steps:
- You choose a local default folder for the built-in file tools.
- You can optionally choose a local connection for Nextcloud.
- You can optionally add other MCP servers from the tool store.
You can postpone the entire onboarding. The default folder and any additional connections can be set later. All folder choices are stored locally only.
The tool store
Click Add tools or Add MCP server. You will first see safe presets that fit the desktop app. Only when you choose Add your own MCP server does the manual form open.
| Preset | Capabilities | Authentication |
|---|---|---|
| Nextcloud | Files, calendar, and contacts | Server address, username, and app password |
| Memory | Preserve and retrieve knowledge later | Local storage |
The store may also show presets for GitHub, Canva, Notion, Supabase, Mailchimp, and other suitable MCP servers. Availability depends on platform, authentication, and information security policy.
Google and Microsoft
Google Workspace and Microsoft 365 are built-in AI-Public connections. They work on web, mobile, and desktop and do not depend on OpenAI or a local MCP preset. After one-time Google or Microsoft consent, the available tools can be used with OpenAI, Claude, Gemini, and Mistral, as far as the chosen model supports tool usage.
Dynamic tool selection
An MCP server can offer dozens of tools. The Desktop Deep Agent selects the relevant tools during the task. This allows multiple large MCP servers to be active without placing all tools simultaneously in the model context.
Secure installation
- The renderer does not start arbitrary shell commands.
- Command, arguments, environment keys, and requested access are checked.
- A native dialog shows what is being started.
- Approved configurations receive a proof of integrity.
- Secrets are encrypted with the operating system’s secure storage.
- Processes stop on disable, removal, logout, and shutdown.
If you remove a server, the locally stored credentials are also deleted.
Status and testing
Under On this computer all active local servers are listed. In the chat settings, local and remote connections are grouped under Connections.
Test with a concrete question, for example:
- “Which folders are in our Nextcloud?”
- “Find the latest emails about this case.”
- “Summarize the documents in this local folder.”
Troubleshooting
- Server active, but no tools: restart the local runtime and check the server status.
- Authentication missing: open the server in Preferences → Tools and choose reconnect.
- Nextcloud not working: use the base URL of the environment and a separate app password.
- Local files not accessible: check if the active working folder still exists and reselect it via the dashboard if necessary.
- Many tools active: keep dynamic tool selection enabled and specify the desired source in your question.
Add your own stdio server
Preferably use an organization-approved preset. When installing manually, check executable, arguments, environment keys, filesystem access, and read or write capabilities.
See also
Access to local folders
The built-in file tools can only read or modify files within the working folder that you explicitly approve via the native folder picker.
Each path is resolved to the canonical location. Tricks with a similar prefix of a neighboring folder and symbolic links that lead outside an approved folder are rejected. After a restart of the local runtime, permissions are resynchronized; without an approved folder, file access is denied by default.
If you ask the AI to delete a file or subfolder, the desktop app moves the item to the system recycle bin. This works on Windows, macOS, and Linux. The approved main folder itself cannot be moved to the recycle bin via the AI.
