RS Filesystem

Exposes MCP access to Rust-based filesystem tools, enabling directory queries and filesystem prompts within MCP clients.

rust

21

GitHub Stars

rust

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "fellowtraveler-rs_filesystem": {
      "command": "/path/to/rs_filesystem",
      "args": [
        "--mcp"
      ],
      "env": {
        "MCP_RS_FILESYSTEM_ALLOWED_DIRECTORIES": "*/path/number/one:/path/number/two"
      }
    }
  }
}

You enable and use the RS Filesystem MCP Server to access and manage Rust-based filesystem tools from MCP clients. This server runs locally and communicates with your client to perform filesystem-related actions within controlled directories, making automation and scripting in MCP workflows practical and safe.

How to use

To use this MCP server with your client, first ensure the server is wired into your MCP client configuration. You enable the server with the MCP flag and point your client to the local command that runs the server. The server will restrict operations to directories you explicitly allow.

Next, place the provided configuration into your client’s MCP server setup under the mcpServers section. This enables the server and passes the necessary environment variable with the allowed directories. After configuring, start the client and verify that the rs_filesystem MCP server is available in the MCP server list.

If you want to monitor the server’s activity, you can tail the RFC logging file to watch recent events and diagnostic messages as you work with the filesystem tools.

How to install

Prerequisites: your MCP client must support MCP servers and be configured to run local stdio MCP servers. Ensure the client has access to the filesystem paths you will specify in the allowed directories and that you have permission to execute the rs_filesystem binary.

Locate or prepare your MCP client configuration area where MCP servers are defined.
Add the stdio MCP server entry using the exact command and arguments shown in the configuration snippet. This config uses the rs_filesystem executable and passes the --mcp flag.
Set up the environment variable that restricts access to allowed directories. Ensure the value is a colon-separated list of absolute paths you want to permit.
Save the configuration and start or reload your MCP client to pick up the new server configuration.

Configuration example and notes

{
  "mcpServers": {
    "rs_filesystem": {
      "command": "/path/to/rs_filesystem",
      "args": [
        "--mcp"
      ],
      "env": {
        "MCP_RS_FILESYSTEM_ALLOWED_DIRECTORIES": "/path/number/one:/path/number/two"
      }
    }
  }
}

Troubleshooting and tips

If you need to check logs, tail the log file to watch recent entries for the RS Filesystem MCP server. This helps you confirm that the server started correctly and is handling requests from your client.

Ensure the MCP RS Filesystem server has permission to execute the binary and access the allowed directories. If you encounter permission errors, review file permissions and the ownership of the rs_filesystem binary and the target directories.

Available tools

filesystem

Filesystem tools exposed by the MCP server for directory operations, resource prompts, and related actions within MCP clients.