Best for
- MCP clients that need controlled local file access
- Developers who want to explicitly constrain filesystem operations
M
46FMRS · D
The source identifies this as an active filesystem MCP server supporting three transports and requiring an explicitly configured directory allowlist. It does not document individual tools, client compatibility, or authentication.
This is the filesystem MCP server contained in the UI-TARS-desktop repository. It provides file operations within directories configured through allowed-directories. The manifest lists it as active, version 1.0.0, with stdio, SSE, and Streamable HTTP transports.
Tools
The tool list has not been reviewed yet.
Setup
Use @agent-infra/mcp-server-filesystem from the npm registry and provide the required allowed-directories argument to define the directories permitted for file operations. SSE and Streamable HTTP modes also require a port number, defaulting to 8089.
Fit and risk
Not for
- Workflows that require access to unauthorized directories
- Users seeking a server with documented tool names or broader capabilities
Required permissions
- The server needs file-operation access to the directories listed in allowed-directories
- SSE and Streamable HTTP modes require use of the configured local port
Risks and side effects
- An overly broad allowed-directories value may expand the scope of local files that can be exposed or modified
- When using a local SSE or HTTP endpoint, port and access-scope configuration should be reviewed
- The source does not specify individual filesystem tools, authentication, or authorization mechanisms
Troubleshooting
- Check that the required allowed-directories argument is supplied
- For SSE or Streamable HTTP, check the port configuration; the default is 8089
- Confirm that the client's transport matches the server configuration
- Verify that the configured directories exist and are accessible to the server
Use cases
Giving an MCP client access to files in selected directories
Providing directory-scoped local file operations to agent workflows
Supported clients
Supported clients have not been confirmed yet.