Dyer Md
Point your coding agent at a dyer.md Markdown vault so answers and edits ground in notes you already maintain.
Overview
dyer-md is a MCP server for the Build phase that exposes your dyer.md Markdown vault as a knowledge source for AI agents.
What is this MCP server?
- MCP access to a dyer.md Markdown vault as an AI knowledge source
- npm package dyer-md-mcp version 2.1.1 with stdio transport
- GitHub repository Srishesh-Archik/dyer.md as implementation source
- Lightweight integration pattern for note-first solo builders
- No remote HTTP endpoint listed in catalog metadata—local stdio focus
- Server catalog version 2.1.1
- Single stdio npm package identifier dyer-md-mcp
- GitHub source repository Srishesh-Archik/dyer.md
What problem does it solve?
Your best project knowledge sits in Markdown notes the agent cannot see unless you paste chunks manually every time.
Who is it for?
Solo builders who maintain a dyer.md vault and want a simple stdio MCP hookup without standing up a separate vector database.
Skip if: Teams needing enterprise permissions, real-time collaborative wiki APIs, or deep semantic code search across large monorepos.
What do I get? / Deliverables
After you add dyer-md-mcp, your agent can retrieve and use vault Markdown as grounded context during coding and doc work.
- Agent-accessible retrieval over your dyer.md Markdown corpus via MCP
- Less copy-paste of notes into chat during implementation sessions
Recommended MCP Servers
Journey fit
dyer-md belongs on Build docs because it turns a personal Markdown knowledge vault into an agent-retrievable source while you implement. Docs is the canonical shelf: the server’s purpose is vault-backed Markdown knowledge, not runtime monitoring or distribution.
How it compares
Markdown vault knowledge MCP, not a codebase indexer like semantic grep tooling.
Common Questions / FAQ
Who is dyer-md for?
dyer-md is for developers who use dyer.md for notes and want Claude Code, Cursor, or other MCP clients to read that vault as structured knowledge.
When should I use dyer-md?
Use dyer-md during Build (and ongoing iteration) whenever agent answers should cite your Markdown runbooks, specs, and checklists instead of inventing details.
How do I add dyer-md to my agent?
Configure stdio MCP with the dyer-md-mcp npm package (version 2.1.1 in catalog) pointing at your vault per the dyer.md project setup on GitHub.