basic-fns-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASIC_FNS_HOST | No | HTTP bind address | 127.0.0.1 |
| BASIC_FNS_PORT | No | HTTP bind port | 8080 |
| BASIC_FNS_ROOT | No | Sandbox root; all paths resolve under it | current working directory |
| BASIC_FNS_READ_ONLY | No | Disable write and edit | false |
| BASIC_FNS_TRANSPORT | No | http or stdio | http |
| BASIC_FNS_ALLOW_BASH | No | Do not register the bash tool (false disables bash) | true |
| BASIC_FNS_MAX_OUTPUT | No | Cap any tool result to this length | 100000 |
| BASIC_FNS_BASH_TIMEOUT | No | Default shell timeout in seconds | 120 |
| BASIC_FNS_MAX_READ_BYTES | No | Refuse read for files larger than this | 2000000 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| readA | Read a text file and return its contents with cat-style line numbers. |
| grepB | Search file contents by regex. |
| findA | Find files or directories by glob-style name match. |
| lsA | List the contents of a directory. |
| writeA | Create or overwrite a file atomically (temp file + os.replace). |
| editA | Replace old_string with new_string in a text file. |
| bashA | Execute a shell command and return exit code, stdout, and stderr. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
read, grep, find, and ls each target a distinct operation (reading content, searching content, finding files by name, listing directories), but the generic bash tool can perform all of these actions, creating overlap and ambiguity about when to use the specialized tools versus bash.
All tool names are single lowercase verbs (read, grep, find, ls, write, edit, bash) following a consistent Unix-command style. The naming pattern is uniform and predictable.
With 7 tools, the server is well-scoped for a basic file operations server. Each tool addresses a core operation (read, write, edit, search, list), and the count is within the ideal range.
The server covers create (write), read (read), and update (edit) but lacks an explicit delete, move, or copy operation. The bash tool can work around these gaps, but the dedicated surface is incomplete for full file lifecycle management.