Md Md
Inject md.md team knowledge into Claude Code or Cursor so coding agents answer with your internal docs and decisions, not generic guesses.
Overview
md-md is an MCP server for the Build phase that provides md.md team knowledge context to AI coding assistants.
What is this MCP server?
- MCP server for md.md backend—team knowledge context for AI assistants
- npm package md-md-mcp-server v1.0.0 with stdio transport
- Requires MD_MD_API_KEY; optional MD_MD_API_URL, MD_MD_TEAM_ID, MD_MD_WORKSPACE_ID scoping
- Reduces hallucinated architecture answers when your canon lives in md.md
- Context provider MCP—not a wiki migration or doc authoring skill by itself
- Server version 1.0.0
- Up to 4 environment variables documented: 1 required secret (MD_MD_API_KEY) and 3 optional scope/URL vars
- npm identifier md-md-mcp-server; stdio transport
What problem does it solve?
Your agent invents stack details because it cannot see the decisions and docs your team already stored in md.md.
Who is it for?
Indie teams using md.md as a living knowledge base who want MCP-grounded coding and doc tasks in Claude Code or Cursor.
Skip if: Builders without an md.md account/API key or those who only need local README files with no shared knowledge service.
What do I get? / Deliverables
Once MD_MD_API_KEY and scope env vars are configured, tool calls can fetch md.md-backed context so implementation chat matches your team knowledge.
- Agent tool access to md.md team knowledge context
- Scoped queries when MD_MD_TEAM_ID or MD_MD_WORKSPACE_ID are set
- More consistent implementation answers aligned with stored team docs
Recommended MCP Servers
Journey fit
Canonical shelf is Build → Docs because the server’s job is supplying team knowledge context while you implement features and write technical documentation. Docs is the right primary subphase for a knowledge-base MCP that grounds agents in md.md content during implementation and spec work.
How it compares
Team knowledge MCP feed, not a generic filesystem RAG skill or Notion clone.
Common Questions / FAQ
Who is md-md MCP for?
Solo founders and small teams on md.md who want their coding agents to read team-scoped knowledge through MCP instead of stale prompts.
When should I use md-md MCP?
While building and documenting—when specs, runbooks, and architecture notes in md.md should inform every agent turn—and during review or ops chats that need the same canon.
How do I add md-md to my agent?
Set MD_MD_API_KEY (and optional MD_MD_API_URL, MD_MD_TEAM_ID, MD_MD_WORKSPACE_ID), install md-md-mcp-server from npm, and register the stdio MCP server in your client.