Skip to main content
Glama
devrandom

mcp-fstools

by devrandom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
readA

Read a file, optionally from offset (1-based) for limit lines.

Returns line-numbered content like cat -n. Records the file's content hash so a subsequent edit can enforce must-read-first.

editA

Replace old_string with new_string in file_path.

Requirements (matches opencode):

  • You must call read on this file in the same session first.

  • old_string must appear exactly once in the current file content. Provide more surrounding context if it isn't unique.

  • The file must not have changed since the last read.

Returns a unified diff of the change.

writeA

Write content to file_path, overwriting any existing content.

Parent directories are created if missing. The file's new content hash is recorded so a follow-up edit will require a fresh read.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: read retrieves content, edit modifies parts, write overwrites entirely. No overlap in functionality.

Naming Consistency5/5

All tool names are single-word verbs, simple and consistent. No mixing of conventions.

Tool Count4/5

Three tools is minimal but appropriate for a focused file editing server. Each tool earns its place, though more tools could be added for listing or deletion.

Completeness2/5

The tool set lacks fundamental file operations like delete, rename, list, or search. For a general file system server, this is a significant gap.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources