Mermaid Lint MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging for the server (e.g., set to 'mermaid-lint-mcp'). | |
| MERMAID_TIMEOUT | No | Set the default validation timeout in milliseconds (default is 5000). | 5000 |
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 |
|---|---|
| validate_mermaid_diagramB | Validate if a Mermaid diagram can be rendered successfully |
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 1 tool
With only one tool, there is no ambiguity; the tool's purpose is clear and distinct by default.
The single tool name follows a clear verb_noun pattern (validate_mermaid_diagram), which is consistent and readable.
A single tool for a server named 'Mermaid Lint' feels insufficient; typical linting servers include multiple tools for validation, formatting, and configuration.
The surface is severely incomplete; only validation is provided, omitting common linting operations like reporting, fixing, or configuring rules.