Local filesystem
Read and write files within an authorised sandboxed workspace.
Read and write files within an authorised sandboxed workspace.
What this connection offers
Use the filesystem exposed by the configured tool service. Its allowed locations determine access; this connection does not grant general access to your computer’s disk.
| Detail | Value |
|---|---|
| Available uses | Assistant tools |
| Sign-in | Credentials or access key |
| Catalogue identifier | io.modelcontextprotocol.filesystem |
| Connection scope | user |
| Direction | source |
Connect
- Open Connections, choose to connect a service, and select Local filesystem with the uses listed above.
- Give the connection a recognisable name.
- Fill the settings below in the connection form. Secret fields belong in the credential form, never in chat.
- Check the connection status and run a connection test where offered.
- Select this saved connection in the app, workflow step, storage browser, or Assistant task that needs it.
Connection settings
| Setting | Type | Required | Secret | Explanation |
|---|---|---|---|---|
Workspace path (workspace_path) | text | yes | no | Absolute path that the sandboxed MCP server may access. |
Update credentials
Rotate credentials on the saved connection, then test and check a dependent task. A hidden stored secret is not an empty secret. Supply a replacement only when you intend to change it.
Diagnose a failure
Check the connected account, its permission to the target, the selected folder, table or collection, and the connection’s current status. A successful sign-in is not proof that a particular resource is shared with that account. An empty search or folder page is not necessarily an authentication error. Revoke access when it is no longer needed; deleting the connection can also affect its tools and synced data. See connection lifecycle.