mcp-server-markdown
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesA | List all .md files in a directory recursively. Returns relative paths sorted alphabetically. |
| search_docsA | Full-text search across all .md files in a directory. Returns file, line number, and matching line. Limited to 50 results. |
| get_sectionA | Extract a section by heading from a markdown file. Returns content from that heading until the next heading of same or higher level. |
| list_headingsA | List all headings (# through ######) in a markdown file as a table of contents. |
| find_code_blocksB | Find all fenced code blocks in a markdown file. Optionally filter by language (e.g. typescript, python). |
| get_frontmatterB | Parse YAML frontmatter (between --- delimiters) at the start of a markdown file. Returns key-value metadata. |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: find_code_blocks extracts code, get_frontmatter extracts metadata, get_section extracts content by heading, list_files lists files, list_headings lists headings, and search_docs performs full-text search. The descriptions make it easy to tell them apart.
All tools follow a consistent verb_noun pattern with snake_case: find_code_blocks, get_frontmatter, get_section, list_files, list_headings, and search_docs. The naming is predictable and readable throughout.
With 6 tools, the server is well-scoped for markdown processing, covering common operations like listing files, extracting sections, searching, and parsing metadata. Each tool earns its place without being too sparse or bloated.
The tool set covers key markdown operations well, including reading, searching, and extracting content. Minor gaps exist, such as no tools for creating or modifying markdown files, but agents can work around this for analysis-focused workflows.