Markdown3D MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transform_to_nm3B | Transform markdown to NM3 (returns full XML - may truncate for large docs >300 nodes) |
| transform_to_nm3_chunkedB | Transform markdown to NM3 with chunked output (prevents truncation for large docs) |
| assemble_chunksB | Assemble chunked output into final NM3 file |
| get_chunk_statusC | Check status of chunked output |
| validate_nm3C | Validate NM3 XML for compliance with spec |
| get_performance_statsC | Get performance and cache statistics |
| clear_cacheC | Clear all caches |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: transformation (normal and chunked), validation, assembly, cache management, status checking, and performance stats. The only potential overlap is between the two transform tools, but the chunked variant's purpose is explicitly differentiated.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., assemble_chunks, clear_cache, get_performance_stats, transform_to_nm3). The naming is predictable and uniform.
With 7 tools, the set is well-scoped for a server focused on transforming markdown to NM3. Each tool serves a specific function in the workflow, and there are no extraneous or missing tools relative to the domain.
The tool set covers the core transformation lifecycle (normal and chunked), validation, and assembly, plus utility functions (cache, status, performance). A minor gap is the lack of a reverse conversion (NM3 to markdown), but this is not part of the stated purpose.