markdown-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_markdownC | Read a validated Markdown file or exact #section/#--- block. |
| list_sectionsC | List Markdown headings and generated anchors in source order. |
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 2 tools
read_markdown returns Markdown content, while list_sections returns heading structure and anchors. Their purposes are clearly distinct with no overlapping behavior, so an agent can easily select the correct tool.
Both tools use a consistent snake_case verb_noun pattern: read_markdown and list_sections. There are no naming style deviations.
Two tools is borderline thin for a general Markdown MCP server, even if they are well-scoped for basic reading and navigation. The set feels minimal rather than comfortably complete.
The surface covers reading a file, reading a section/block, and listing sections, which is reasonable for read-only navigation. However, it lacks common lifecycle operations such as creating, updating, or searching Markdown content, so notable gaps remain for a broader Markdown server.