md-reader-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MDR_API_URL | No | The URL of the Markdown Reader & Editor local API. | http://127.0.0.1:41100 |
| MDR_API_TOKEN | Yes | The bearer token shown in Markdown Reader Preferences under Local API. |
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_connectionsA | List the NAS / server connections configured in Markdown Reader (no passwords). |
| add_connectionA | Add a NAS / server connection to Markdown Reader. The password is stored in the OS keychain by the app. |
| remove_connectionA | Delete a connection (and its stored password) from Markdown Reader. |
| test_connectionB | Check that a configured connection can reach its server. |
| list_notesA | List the Markdown files (as a tree) under a folder on a connection. |
| read_noteA | Read a Markdown note. Returns its content, front matter, tags, and optionally HTML. |
| write_noteB | Create or overwrite a Markdown note with the given content. |
| search_notesB | Full-text search across the Markdown files on a connection. |
| backlinksA | List the notes that link to a given note (Markdown links or [[wikilinks]]). |
| list_tagsB | Every #tag and front-matter tag across a connection, with counts and file lists. |
| render_markdownA | Render arbitrary Markdown to HTML using Markdown Reader’s engine (GitHub alerts, KaTeX, tags, task lists). Also returns front matter and tags. |
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 11 tools
Most tools have clear, distinct purposes. Minor overlap exists between read_note and render_markdown (both can return note content/HTML), but overall the query, write, and connection-management tools are clearly separated.
Names mostly follow a consistent verb_noun pattern (list_notes, read_note, write_note, add_connection). The exception is 'backlinks', which is a noun rather than a verb_noun, making it slightly inconsistent.
11 tools is well-scoped for a note-taking server with connection management. Each tool serves a distinct, practical function without unnecessary bloat.
Core note workflows (read, write, search, list, render, tags, backlinks) and connection lifecycle (add, remove, list, test) are covered. Missing explicit delete/rename note operations, though overwriting via write_note mitigates this gap.