Skip to main content
Glama
deenesjakoruzh
jinzcdev

Markmap MCP Server

by jinzcdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

마크맵 MCP 서버

샘플 마인드맵

NPM 버전 GitHub 라이센스 대장간 배지 중국어(중국어) 별

Markmap MCP 서버는 마크다운 텍스트를 오픈 소스 프로젝트인 마크맵 (markmap )을 기반으로 한 대화형 마인드맵으로 원클릭 변환할 수 있는 모델 컨텍스트 프로토콜(MCP)을 기반으로 합니다. 생성된 마인드맵은 풍부한 대화형 작업을 지원하며 다양한 이미지 형식으로 내보낼 수 있습니다.

특징

  • 🌠 마크다운을 마인드맵으로 변환 : 마크다운 텍스트를 대화형 마인드맵으로 변환

  • 🖼️ 다양한 포맷으로 내보내기 : PNG, JPG, SVG 이미지로 내보내기 지원

  • 🔄 대화형 작업 : 확대/축소, 노드 확장/축소 및 기타 대화형 기능 지원

  • 📋 마크다운 복사 : 원본 마크다운 콘텐츠의 원클릭 복사

  • 🌐 자동 브라우저 미리보기 : 생성된 마인드 맵을 브라우저에서 자동으로 여는 옵션

Related MCP server: MindManager MCP Server

필수 조건

  1. Node.js 런타임 환경

설치

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Markmap MCP Server를 자동으로 설치하려면:

지엑스피1

수동 설치

# Install from npm
npm install @jinzcdev/markmap-mcp-server -g

# Basic run
npx -y @jinzcdev/markmap-mcp-server

# Specify output directory
npx -y @jinzcdev/markmap-mcp-server --output /path/to/output/directory

또는 저장소를 복제하여 로컬에서 실행할 수 있습니다.

# Clone the repository
git clone https://github.com/jinzcdev/markmap-mcp-server.git

# Navigate to the project directory
cd markmap-mcp-server

# Build project
npm install && npm run build

# Run the server
node build/index.js

용법

MCP 클라이언트 구성 파일에 다음 구성을 추가합니다.

{
  "mcpServers": {
    "markmap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@jinzcdev/markmap-mcp-server",
        "--output",
        "/path/to/output/directory"
      ]
    }
  }
}

[!팁]

이 서비스는 다음과 같은 환경 변수를 지원합니다.

  • MARKMAP_DIR : 마인드 맵의 출력 디렉토리를 지정합니다(선택 사항, 기본값은 시스템 임시 디렉토리)

우선 순위 메모 :

--output 명령줄 인수와 MARKMAP_DIR 환경 변수가 모두 지정된 경우, 명령줄 인수가 우선합니다.

사용 가능한 도구

마크다운-마인드맵

마크다운 텍스트를 대화형 마인드 맵으로 변환합니다.

매개변수:

  • markdown : 변환할 Markdown 콘텐츠(필수 문자열)

  • open : 생성된 마인드맵을 브라우저에서 자동으로 열지 여부(선택 사항인 부울, 기본값은 false)

반환 값:

{
  "content": [
    {
      "type": "text",
      "text": "JSON_DATA_OF_MINDMAP_FILEPATH"
    }
  ]
}

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다.

Available Tools

1 tool
markdown_to_mindmapB

Convert a Markdown document into an interactive mind map

ParametersJSON Schema
NameRequiredDescriptionDefault
markdownYesMarkdown content to convert into a mind map
openNoWhether to open the generated mind map in a browser (default: false)

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the conversion action but fails to describe key behavioral traits such as what format the mind map output takes (e.g., file, URL, visual representation), whether the conversion is reversible, any rate limits, or error handling. This leaves significant gaps for an agent to understand how to interact with the tool effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded with the core action, making it easy to parse and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a conversion tool with no annotations and no output schema, the description is incomplete. It lacks details on the output format (e.g., how the mind map is returned or accessed), potential side effects, or any prerequisites for successful conversion. This leaves the agent with insufficient context to use the tool reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents both parameters ('markdown' and 'open') thoroughly. The description adds no additional meaning beyond what the schema provides, such as examples of Markdown content or implications of the 'open' parameter. Baseline 3 is appropriate as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Convert') and the resources involved ('Markdown document' into 'interactive mind map'), leaving no ambiguity about what the tool does. It distinguishes the transformation process explicitly, which is sufficient even without sibling tools for comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when converting Markdown to a mind map, but provides no explicit guidance on when to use this tool versus alternatives (e.g., other conversion tools or manual methods). Since there are no sibling tools listed, this omission is less critical, but it still lacks proactive usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedmarkdown_to_mindmap
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct and singular.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (markdown_to_mindmap), establishing a consistent naming convention for the server.

Tool Count2/5

One tool is too few for a server's typical scope, as it limits functionality and may indicate an incomplete or overly narrow implementation. However, it is not as extreme as a trivial single tool, so it avoids the lowest score.

Completeness3/5

The tool provides a core conversion function, but there are notable gaps such as missing operations for editing, saving, or loading mind maps, which could hinder agent workflows. The surface is functional but not fully comprehensive.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers