any2mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| word_countA | Count words, lines, and characters in a string. Pure computation - no side effects at all. |
| read_project_fileB | Read a UTF-8 text file from disk, truncating past max_bytes. |
| list_directoryC | List the entries of a directory, sorted. |
| write_noteA | Write text to path, replacing any existing file. Returns bytes written. |
| parse_json_fileC | Load and return the JSON value stored in a file. |
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 5 tools
word_count is pure computation, list_directory is distinct, and write_note is the sole writer, so most tools are easy to tell apart. read_project_file and parse_json_file overlap somewhat since both read files from disk, though the parsed-JSON vs raw-text distinction helps.
Four tools follow a clear verb_noun pattern (read_project_file, list_directory, write_note, parse_json_file). word_count deviates as a noun_noun form, a minor inconsistency in an otherwise predictable scheme.
Five tools is well-scoped for a lightweight file/text/JSON utility server, with each tool earning its place and no redundancy.
The surface covers reading, listing, writing, JSON parsing, and word counting, but has no delete/remove, no JSON writing or in-place edit, and no directory creation, leaving notable lifecycle gaps for a file-oriented toolkit.