mdgraph

mdgraph

Provides MCP tools to scan and navigate markdown repositories, offering graph-based overview, document reading, context retrieval, and orphan detection.

Category
访问服务器

README

mdgraph

Scan a repo's markdown into a graph, visualize it in the browser, and expose it to Claude (or any MCP host) as a navigation index.

One data model — { nodes, edges } — with three consumers:

              scan  (the only hard part)
                 │  emits { nodes, edges }
      ┌──────────┼───────────┐
      ▼          ▼           ▼
   graph.json  browser     MCP server
   (a file)   (viewer)   (agents read it)

Insights, reachability, and orphans are all derived from the model at read time. Nodes and edges stay dumb.

The model

node = { id, label, path, type, cluster, content }   // type: root | ai | doc
edge = { source, target, sourceLine, context }        // context = the line the link lives on

type is assigned by filename convention (README.md → root, CLAUDE.md/AGENTS.md/*.mdc → ai, else doc). Edges come from actual links in the text — standard [x](./y.md) and [[wikilinks]] — not folder membership, so a file in docs/ that links across the tree still connects across the tree. Folders only drive cluster (coloring/grouping).

Install & run

No install needed — run it straight with npx:

npx @emmd474/mdgraph scan .            # print the graph as JSON
npx @emmd474/mdgraph view .            # open the interactive graph in a browser
npx @emmd474/mdgraph scan . --out graph.json

Or install globally to get a plain mdgraph command:

npm install -g @emmd474/mdgraph
mdgraph view ./my-repo
mdgraph scan ./my-repo --out graph.json

dir defaults to the current directory. view takes --port (default 4173).

Commands

Command What it does
mdgraph scan [dir] Build the graph, print JSON to stdout (or write with --out).
mdgraph view [dir] Serve the interactive graph at localhost:4173; re-scans on refresh.
mdgraph mcp [dir] Run the MCP server over stdio, for Claude and other agents.

Expose to Claude (MCP)

Claude Desktop — add to claude_desktop_config.json:

{
  "mcpServers": {
    "mdgraph": {
      "command": "npx",
      "args": ["-y", "@emmd474/mdgraph", "mcp", "/abs/path/to/your/repo"]
    }
  }
}

Claude Code:

claude mcp add mdgraph -- npx -y @emmd474/mdgraph mcp /abs/path/to/your/repo

Restart the host and Claude gets four tools:

Tool Purpose
get_project_map Content-free overview: types, clusters, link counts, orphan/reachable flags, edges. The cheap way to orient.
read_doc Raw markdown of one doc by path.
get_context Everything reachable from an entry doc, in read order — the exact set to load to understand it. includeContent: true bundles the markdown.
find_orphans Docs nothing links to.

The point: an agent calls get_project_map to orient, then get_context("README.md") to pull only the docs the task needs — instead of dumping every .md into context.

Publishing (for maintainers)

The name mdgraph is taken on npm, so this publishes scoped under your account:

# 1. set the scope to YOUR npm username (edit "name" in package.json if not @emmd474)
npm whoami          # confirm you're logged in; else: npm login
npm publish --access public

Scoped packages are private by default, so --access public is required the first time. To ship an update, bump the version and publish again:

npm version patch   # 0.1.0 -> 0.1.1, also creates a git tag
npm publish

npm pack --dry-run shows exactly what ships (currently 7 files, ~16 kB — no node_modules, no test repo, thanks to the files allowlist).

Try it on the example

git clone <this repo> && cd mdgraph && npm install
node cli.mjs view testrepo
node cli.mjs scan testrepo

What's real vs. next

Tested and working: the scanner (md + wikilink extraction, code-fence skipping, convention typing, orphan detection), the browser viewer, and all four MCP tools over a live stdio handshake.

Next, roughly in order:

  • Harden link parsing — the scanner is line-based and skips fenced blocks, but an inline code span (`[x](y)`) can still yield a false link. Swap in a real markdown AST (remark + unist-util-visit) when you want precision; the emitted shape stays identical.
  • Manual edges — let the viewer write related: into a file's frontmatter, read as a third edge source.
  • Frontmatter tags as a cluster source alongside folders.
  • --watch on view to push graph updates over server-sent events.

MIT licensed.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选