Mermaid is an MCP server with 25 tools an agent can call, among them create_issue, create_pr, generate_jira_kanban_board. It answers at https://mcp.mermaidchart.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
MCP server for Mermaid diagram validation and rendering
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
create_issue | Create an issue in a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN with issues write if creating issues in private repos. Inputs: owner, repo, title, body, labels, clientName |
create_pr | Create a new branch (git ref), one commit from the base tree with your file changes, then open a pull request in the same repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN with `contents: write` (and no existing branch with the sa Inputs: owner, repo, headBranch, baseBranch, title, body |
generate_jira_kanban_board | Generate a Mermaid kanban board from Jira issues. Issues are grouped into columns by their current status and ordered by workflow stage (To Do → In Progress → Done). Each card shows the issue summary and is a clickable link to the ticket, w Inputs: projectKey, sprint, assignee, issueType, maxResults, clientName |
generate_ticket_dependency_tree | Generate a Mermaid flowchart that visualises Jira issue dependency links for a project. Each node shows the ticket key, summary, and status, and is a clickable link to the ticket. Dashed nodes represent issues linked from outside the curren Inputs: projectKey, status, assignee, reporter, sprint, createdAfter |
generate_ticket_diagram | Generate a Mermaid flowchart centred on a single Jira ticket. Fetches the ticket's subtasks, parent, issue links, and recent comments in one call. The focal ticket is highlighted in indigo; subtasks are grouped in a subgraph; issue links us Inputs: ticketKey, colorMode, clientName |
generate_ticket_timeline | Generate a Mermaid diagram showing the history of a single Jira ticket using its changelog. Two views are available: - **state**: stateDiagram-v2 showing all status transitions with dates and authors, nodes coloured by status category. - ** Inputs: ticketKey, view, clientName |
get_diagram_summary | Generate a concise summary for a Mermaid diagram based on its content. This tool provides prompts for the LLM to generate a brief summary (2-4 sentences) highlighting the primary flow, key decisions, and outcomes. Inputs: diagramContent, contextHint, clientName |
get_diagram_title | Generate a descriptive title for a Mermaid diagram based on its content. This tool analyzes the diagram structure and content to suggest an appropriate title. Inputs: diagramContent, diagramType, currentTitle, clientName |
get_issue_comments | List comments on an issue by issue number. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Inputs: owner, repo, issue_number, per_page, page, clientName |
get_mermaid_syntax_document | Get comprehensive syntax documentation and examples for a specific Mermaid diagram type. Returns the official Mermaid.js documentation with syntax rules, examples, and usage instructions for the requested diagram type. Inputs: diagramType, clientName |
get_notion_mermaid_diagram_by_block_id | Retrieve a single Mermaid diagram block by its block ID. Returns the diagram code and optional caption. Inputs: blockId, clientName |
get_notion_page_mermaid_diagrams | Extract all Mermaid code blocks from a Notion page. Returns block ID, diagram code, and optional caption for each block. Inputs: pageUrl, clientName |
get_pull_comments | Get all pull request comments: both issue/PR thread comments and inline review comments, with a `type` of `issue_thread` or `review` per item. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Inputs: owner, repo, pull_number, per_page, page, clientName |
insert_notion_mermaid_diagram | Append a Mermaid diagram as a code block to a Notion page. The block is added at the end of the page content. Inputs: pageUrl, code, caption, clientName |
list_branches | List or resolve branch names. **List mode (default):** one `GET /repos/.../branches?per_page=100&page=1` — at most 100 names, A–Z sorted in the response; `has_more` if a full page was returned. **Resolve mode:** set `branch_name` for a sing Inputs: owner, repo, branch_name, clientName |
list_issues | List issues for a repository (excludes pull requests). REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Inputs: owner, repo, state, labels, sort, direction |
list_mermaid_files | List .mmd Mermaid files in a GitHub repository (code search with tree fallback). REQUIRES: `Github-Token` header (HTTP) or GITHUB_TOKEN / GH_TOKEN. Inputs: owner, repo, ref, clientName |
list_pulls | List pull requests for a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Inputs: owner, repo, state, per_page, page, clientName |
list_repos | List GitHub repositories for the authenticated user, or for an organization when `org` is set. REQUIRES: `Github-Token` header (HTTP) or `GITHUB_TOKEN` / `GH_TOKEN` in the server environment. Inputs: org, per_page, page, type, clientName |
list_tools | Lists all available MCP servers and their tools in the workspace. Inputs: clientName |
push_file | Create or update a single file on a given branch in a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN with contents write access. Inputs: owner, repo, path, content, branch, message |
read_mermaid_file | Read a single .mmd file from a GitHub repository. Only paths ending in .mmd are allowed. REQUIRES: `Github-Token` header (HTTP) or GITHUB_TOKEN / GH_TOKEN. Inputs: owner, repo, path, ref, clientName |
search_mermaid_icons | Search for available Mermaid icons by provider or name. Returns icons in ready-to-use format with provider prefixes (e.g., 'aws:arch-amazon-ec2'). PERFORMANCE TIP: For faster searches, start with limit=10 and specific queries. If no suitabl Inputs: query, provider, limit, clientName |
update_notion_mermaid_diagram | Update the Mermaid source code (and optional caption) of an existing mermaid code block by its block ID. Inputs: blockId, code, caption, clientName |
validate_and_render_mermaid_diagram | SIMPLE RENDER TOOL - Renders Mermaid diagrams directly (Mermaid automatically validates during rendering). If successful, returns diagram image. If Mermaid validation fails, returns error details for fixing. One tool, one call, simple workf Inputs: prompt, mermaidCode, diagramType, clientName, useUrlShortener |
Every block below points at https://mcp.mermaidchart.com/mcp. Pick your client and copy.
claude mcp add --transport http mermaid https://mcp.mermaidchart.com/mcp
{
"mcpServers": {
"mermaid": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.mermaidchart.com/mcp"]
}
}
}{
"mcpServers": {
"mermaid": {
"url": "https://mcp.mermaidchart.com/mcp"
}
}
}{
"servers": {
"mermaid": {
"type": "http",
"url": "https://mcp.mermaidchart.com/mcp"
}
}
}{
"context_servers": {
"mermaid": {
"url": "https://mcp.mermaidchart.com/mcp"
}
}
}{
"mcpServers": {
"mermaid": {
"serverUrl": "https://mcp.mermaidchart.com/mcp"
}
}
}{
"mcpServers": {
"mermaid": {
"url": "https://mcp.mermaidchart.com/mcp"
}
}
}name: Mermaid
version: 0.0.1
schema: v1
mcpServers:
- name: Mermaid
type: streamable-http
url: https://mcp.mermaidchart.com/mcp{
"mcpServers": {
"mermaid": {
"httpUrl": "https://mcp.mermaidchart.com/mcp"
}
}
}{
"mcpServers": {
"mermaid": {
"type": "http",
"url": "https://mcp.mermaidchart.com/mcp"
}
}
}{
"mcpServers": {
"mermaid": {
"url": "https://mcp.mermaidchart.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.mermaidchart.com%2Fmcp&type=streamable_http&id=mermaid&name=Mermaid
It answered our last check on 18 October 2026 in 608 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by mermaidchart.com and served from mcp.mermaidchart.com, the vendor's own domain: https://mcp.mermaidchart.com/mcp.
25, as returned by the server's own tools/list on 31 August 2026: create_issue, create_pr, generate_jira_kanban_board, generate_ticket_dependency_tree, generate_ticket_diagram, generate_ticket_timeline, get_diagram_summary, get_diagram_title, and 17 more.
It answered our last check on 18 October 2026 in 608 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.mermaidchart.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.mermaidchart. Endpoint host: mcp.mermaidchart.com. ARD identifier: urn:air:com.mermaidchart:mcp:mermaid-mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.