Filesystem

Filesystem MCP server with SSE capabilities

typescript

5

GitHub Stars

typescript

Language

4 months ago

First Indexed

3 weeks 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": {
    "quantgeekdev-mcp-filesystem": {
      "command": "node",
      "args": [
        "/absolute/path/to/filesystem/dist/index.js"
      ]
    }
  }
}

You run a Model Context Protocol (MCP) server named Filesystem MCP Server. It exposes MCP-powered tools for filesystem-related tasks, letting you plug your server into an MCP client to run tools, manage data, and automate workflows with a consistent, extensible interface.

How to use

You connect to this server from an MCP client to run its tools and receive results. Start by ensuring your server is running, then use the client's tool list to discover available endpoints. You can execute the built-in tool directly and supply input parameters as defined by its schema. The server loads its tools on startup, so start it once you have built the project, and the client can call the available tools by name.

How to install

Prerequisites: Node.js and npm must be installed on your machine. You can verify installations with node -v and npm -v.

Install dependencies for the project.

Build the project.

Run the server in development or production mode as appropriate for your workflow.

npm install
npm run build

Additional sections

Configuration and runtime details are provided here to help you run and test the Filesystem MCP Server. This server is designed to be integrated with MCP clients and accepts tools defined within its runtime. You can build additional tools to extend functionality and adapt to your workflow.

Local development configuration for Claude Desktop users is shown below to enable quick testing against a local runtime. Use this as a starting point while developing locally; switch to the publishing configuration once you are ready to deploy.

{
  "mcpServers": {
    "filesystem": {
      "command": "node",
      "args":["/absolute/path/to/filesystem/dist/index.js"]
    }
  }
}

After you publish a package, you can also run it via a package runner to test from the client side. The example configuration shows how to invoke the server using a package runner.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["filesystem"]
    }
  }
}

Available tools

my_tool

Describes what your tool does