Skip to main content
Glama
deenesjakoruzh
jinzcdev

Markmap MCP Server

by jinzcdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Servidor MCP de Markmap

Mapa mental de muestra

Versión NPM Licencia de GitHub Insignia de herrería 中文文档 Estrellas

El servidor Markmap MCP se basa en el Protocolo de Contexto de Modelo (MCP) , que permite convertir texto Markdown en mapas mentales interactivos con un solo clic, basado en el proyecto de código abierto Markmap . Los mapas mentales generados admiten operaciones interactivas avanzadas y se pueden exportar en varios formatos de imagen.

Características

  • 🌠 Markdown a mapa mental : convierte texto de Markdown en mapas mentales interactivos

  • 🖼️ Exportación multiformato : Soporte para exportar como imágenes PNG, JPG y SVG

  • 🔄 Operaciones interactivas : Soporte para hacer zoom, expandir/contraer nodos y otras funciones interactivas

  • 📋 Copia de Markdown : copia con un solo clic del contenido original de Markdown

  • 🌐 Vista previa automática del navegador : opción para abrir automáticamente los mapas mentales generados en el navegador

Related MCP server: MindManager MCP Server

Prerrequisitos

  1. Entorno de ejecución de Node.js

Instalación

Instalación mediante herrería

Para instalar Markmap MCP Server para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @jinzcdev/markmap-mcp-server --client claude

Instalación manual

# 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

Alternativamente, puede clonar el repositorio y ejecutarlo localmente:

# 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

Uso

Agregue la siguiente configuración a su archivo de configuración de cliente MCP:

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

[!CONSEJO]

El servicio admite las siguientes variables de entorno:

  • MARKMAP_DIR : especifica el directorio de salida para los mapas mentales (opcional, el valor predeterminado es el directorio temporal del sistema)

Nota de prioridad :

Cuando se especifican tanto el argumento de línea de comando --output como la variable de entorno MARKMAP_DIR , el argumento de línea de comando tiene prioridad.

Herramientas disponibles

Markdown a mapa mental

Convierta el texto Markdown en un mapa mental interactivo.

Parámetros:

  • markdown : el contenido de Markdown que se convertirá (cadena obligatoria)

  • open : si se debe abrir automáticamente el mapa mental generado en el navegador (booleano opcional, el valor predeterminado es falso)

Valor de retorno:

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

Licencia

Este proyecto está licenciado bajo la licencia 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