md-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Name for the server (default is folder name) | |
| folder | Yes | Path to the folder containing markdown files |
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 |
|---|---|
| read_fileA | Read a markdown file by its relative path (as shown by list_files / search_markdown), either in full or just one section. |
| rescan_folderA | Manually rescan the folder for new, modified, or deleted markdown files. Use this tool if:
The file watcher (when available) handles this automatically, but this tool provides manual control when needed. Returns: Summary of files found after rescan |
| list_filesB | List available markdown files. |
| search_markdownA | Search for markdown content and return SNIPPETS (not full files). |
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 4 tools
Each tool has a distinct purpose: listing files, searching content, reading specific files or sections, and refreshing the index. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun snake_case pattern (read_file, list_files, search_markdown, rescan_folder), making the API predictable and easy to navigate.
With exactly 4 tools, the server is well-scoped for its purpose. Each tool covers a necessary operation without extraneous additions, fitting comfortably within the ideal range.
For a read-oriented markdown server, the surface is complete: listing, searching, reading, and refreshing the index. There are no obvious dead ends or missing core operations within this scope.