Md Md

Name: Md Md
Author: kedarvartak

by kedarvartakversion 1.0.0i★ –iRuns on your computer

Registry nameio.github.kedarvartak/md-md

Install

Overview

Description from the maker (original English)

MCP server for md.md - provides team knowledge context to AI assistants

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiVery new★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: MD_MD_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: MD_MD_API_KEY, MD_MD_API_URL, MD_MD_TEAM_ID, MD_MD_WORKSPACE_ID

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "md-md": {
      "command": "npx",
      "args": [
        "-y",
        "md-md-mcp-server"
      ],
      "env": {
        "MD_MD_API_KEY": "your-value",
        "MD_MD_API_URL": "your-value",
        "MD_MD_TEAM_ID": "your-value",
        "MD_MD_WORKSPACE_ID": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add md-md --env MD_MD_API_KEY=your-value --env MD_MD_API_URL=your-value --env MD_MD_TEAM_ID=your-value --env MD_MD_WORKSPACE_ID=your-value -- npx -y md-md-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "md-md": {
      "command": "npx",
      "args": [
        "-y",
        "md-md-mcp-server"
      ],
      "env": {
        "MD_MD_API_KEY": "your-value",
        "MD_MD_API_URL": "your-value",
        "MD_MD_TEAM_ID": "your-value",
        "MD_MD_WORKSPACE_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "md-md": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "md-md-mcp-server"
      ],
      "env": {
        "MD_MD_API_KEY": "your-value",
        "MD_MD_API_URL": "your-value",
        "MD_MD_TEAM_ID": "your-value",
        "MD_MD_WORKSPACE_ID": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

MD_MD_API_KEY secret required env
API key for md.md backend
MD_MD_API_URL env
Base URL of md.md backend API
MD_MD_TEAM_ID env
Optional team scope override
MD_MD_WORKSPACE_ID env
Optional workspace scope override

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account kedarvartak, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5747 servers in this category
Published to the registry more recently than 9% of the other 5747 servers in this category
Basic checks equal to or better than 100% of the other 5747 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Md Md safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MD_MD_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 972.7K/wk★ 64.2KUpdated 2 days ago

Computer or cloud

Install

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 18K/wk★ 48.1KUpdated 22 days ago

Runs on your computer

Install

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated 2 months ago

Runs in the cloud✓ exa.ai

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

md.md

md.md is a team intelligence platform that turns internal engineering knowledge into versioned Markdown blocks, then injects the right context into AI-assisted development workflows.

It combines:

A backend registry and policy engine
A React dashboard for authoring and publishing knowledge blocks
An MCP server for IDE and assistant integrations
Integration docs and product design docs

What Problem This Solves

AI coding assistants are strong at general coding but weak on team-specific context. Without shared context, teams repeatedly re-explain standards, architecture decisions, and workflows.

md.md solves this by letting teams:

Author knowledge once
Publish stable versions
Resolve the right context at task time
Reuse the same context across IDEs and AI tools

Repository Structure

app-backend/: NestJS API for auth, block lifecycle, policy resolution, and observability
app-client/: React + Vite dashboard for block authoring, publishing, and resolve preview
mcp-server/: Model Context Protocol server that exposes md.md tools over stdio
ide-integrations/: IDE integration documentation (currently Cursor-focused)
docs/: Product vision, phase plan, and resolution model design docs

High-Level Architecture

Teams author Markdown files inside blocks.
Blocks are versioned and published.
IDE/assistant integrations call resolve tools or APIs with task context.
The backend selects relevant published blocks and composes a payload.
The payload is injected into AI context.
Resolution and usage metadata are logged for observability.

Integration Path

IDE or AI client
MCP protocol over stdio
mcp-server tools
Backend REST API
Postgres persistence (Supabase-compatible)

Core Concepts

Block

A named unit of team knowledge containing one or more Markdown files.

Draft and Published Versions

Draft content can be edited freely. Published versions are stable and intended for consumption.

Scoped Access

Data and permissions are scoped by team and workspace.

Resolution

At usage time, the system resolves and composes relevant published blocks into an AI-ready payload.

Component Details

1) Backend (`app-backend`)

Tech stack:

NestJS 11
PostgreSQL via pg (Supabase-compatible connection)
TypeScript

Responsibilities:

Authentication and authorization
RBAC and API key management
Block CRUD, versioning, publishing, and archiving
Resolution orchestration
Injection log and audit log APIs

Notable backend capabilities:

API key format: mdmd_
Roles: reader, author, admin
Per-block permission overrides
Health and observability endpoints used by MCP

2) Client Dashboard (`app-client`)

Tech stack:

React 19
Vite
TypeScript
MUI + Emotion

Responsibilities:

Create and edit blocks
Manage block files
Publish versions
Preview resolution output
Configure auth/scope information for usage

3) MCP Server (`mcp-server`)

Tech stack:

Node.js + TypeScript
@modelcontextprotocol/sdk
Zod for argument validation

Responsibilities:

Expose md.md capabilities as MCP tools
Forward tool calls to backend APIs
Handle retries, timeouts, and health checks

Primary tools include:

resolve_context
attach_blocks
list_blocks
get_block
health_check
Block lifecycle tools (create_block, update_block, publish_block, etc.)
Access and observability tools (whoami, list_injection_logs)

4) IDE Integrations (`ide-integrations`)

Contains setup patterns for connecting editors to the MCP server.

Current documented integration:

Cursor (MCP client configuration)

5) Product and Design Docs (`docs`)

idea_1.0.md: product rationale and system vision
phases_1.0.md: implementation roadmap (phase-oriented)
resolution_model.md: detailed target model for selection, ordering, and composition

Local Development Setup

Prerequisites

Node.js 18+
npm
PostgreSQL database (Supabase Postgres recommended)

1) Backend

cd app-backend

npm install

Create app-backend/.env with at least:

SUPABASE_DATABASE_URL=postgresql://<user>:<password>@<host>:<port>/<db>

Start backend:

npm run start:dev

2) Create Admin API Key

From app-backend:

npm run create-admin -- \

--email admin@yourcompany.com \ --name "Admin User" \ --team team-alpha \ --workspace workspace-core

Save the generated mdmd_... key securely.

3) Client Dashboard

cd ../app-client

npm install npm run dev

4) MCP Server

cd ../mcp-server

npm install npm run build npm start

Set environment variables for MCP runtime (either shell or IDE config):

MD_MD_API_URL=http://localhost:3000

MD_MD_API_KEY=mdmd_your_key_here

Common Developer Workflows

Backend

cd app-backend

npm run start:dev npm run build npm run test npm run test:e2e npm run lint

Client

cd app-client

npm run dev npm run build npm run lint npm run preview

MCP Server

cd mcp-server

npm run dev npm run build npm start

Security and Secrets

Do not commit API keys or token files.
Keep secrets in environment files or secure secret managers.
Use least-privilege API keys for integrations.
Rotate keys regularly.
Review audit logs for sensitive actions.

Recent local ignore defaults in mcp-server/.gitignore include:

.mcpregistry_github_token
.mcpregistry_registry_token

Current Product Status

Implemented:

End-to-end block lifecycle (create, edit, publish)
Dashboard authoring and resolve preview
Backend RBAC and API key management
MCP server with tooling for context resolution and block operations

In progress or planned:

Smarter policy-based contextual selection and ordering
Expanded IDE integrations
Additional analytics and governance features

Where To Go Next

Backend implementation and auth docs: app-backend/docs/
MCP usage and integration details: mcp-server/README.md
IDE setup notes: ide-integrations/README.md
Product vision and roadmap: docs/

License

See license declarations in each package (app-backend, app-client, mcp-server).

Md Md

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

md.md

What Problem This Solves

Repository Structure

High-Level Architecture

Integration Path

Core Concepts

Block

Draft and Published Versions

Scoped Access

Resolution

Component Details

1) Backend (app-backend)

2) Client Dashboard (app-client)

3) MCP Server (mcp-server)

4) IDE Integrations (ide-integrations)

5) Product and Design Docs (docs)

Local Development Setup

Prerequisites

1) Backend

2) Create Admin API Key

3) Client Dashboard

4) MCP Server

Common Developer Workflows

Backend

Client

MCP Server

Security and Secrets

Current Product Status

Where To Go Next

License

1) Backend (`app-backend`)

2) Client Dashboard (`app-client`)

3) MCP Server (`mcp-server`)

4) IDE Integrations (`ide-integrations`)

5) Product and Design Docs (`docs`)