mcp server
mermaid-mcp
MCP server for Mermaid diagram validation and rendering
Description as published by the maintainer. Source
- version 1.0.0
- archived
archived — The linked repository returns 404. It was deleted, renamed or made private.
What this server can do
25 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
create_issue(body, repo, owner, title, labels, clientName)- Create an issue in a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN with issues write if creating issues in private repos. Required: owner, repo, title, clientName.
create_pr(body, repo, files, owner, title, baseBranch, clientName, headBranch, commitMessage)- 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 same `headBranch` name). Required: owner, repo, headBranch, title, body, commitMessage, files, clientName.
generate_jira_kanban_board(sprint, assignee, issueType, clientName, maxResults, projectKey)- 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, with optional assignee and priority badges. Required: projectKey, clientName.
generate_ticket_dependency_tree(sprint, status, assignee, reporter, colorMode, clientName, maxResults, projectKey, createdAfter, createdBefore, useUrlShortener)- 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 current filter set. Required: projectKey, clientName.
generate_ticket_diagram(colorMode, ticketKey, clientName)- 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 use colour-coded arrows (red thick = blocks, cyan dashed = relates to); comments appear in a rose subgraph. Required: ticketKey, clientName.
generate_ticket_timeline(view, ticketKey, clientName)- 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. - **timeline** (default): Mermaid timeline grouped by month, showing status changes, assignee changes, priority changes, sprint moves, and resolutions. Required: ticketKey, clientName.
get_diagram_summary(clientName, contextHint, diagramContent)- 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. Required: diagramContent, clientName.
get_diagram_title(clientName, diagramType, currentTitle, diagramContent)- 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. Required: diagramContent, clientName.
get_issue_comments(page, repo, owner, per_page, clientName, issue_number)- List comments on an issue by issue number. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Required: owner, repo, issue_number, clientName.
get_mermaid_syntax_document(clientName, diagramType)- 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. Required: diagramType, clientName.
get_notion_mermaid_diagram_by_block_id(blockId, clientName)- Retrieve a single Mermaid diagram block by its block ID. Returns the diagram code and optional caption. Required: blockId, clientName.
get_notion_page_mermaid_diagrams(pageUrl, clientName)- Extract all Mermaid code blocks from a Notion page. Returns block ID, diagram code, and optional caption for each block. Required: pageUrl, clientName.
get_pull_comments(page, repo, owner, per_page, clientName, pull_number)- 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. Required: owner, repo, pull_number, clientName.
insert_notion_mermaid_diagram(code, caption, pageUrl, clientName)- Append a Mermaid diagram as a code block to a Notion page. The block is added at the end of the page content. Required: pageUrl, code, clientName.
list_branches(repo, owner, clientName, branch_name)- 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 single `GET` branch (404 if missing). At most one GitHub API call. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Required: owner, repo, clientName.
list_issues(page, repo, sort, owner, since, state, labels, per_page, direction, clientName)- List issues for a repository (excludes pull requests). REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Required: owner, repo, clientName.
list_mermaid_files(ref, repo, owner, clientName)- List .mmd Mermaid files in a GitHub repository (code search with tree fallback). REQUIRES: `Github-Token` header (HTTP) or GITHUB_TOKEN / GH_TOKEN. Required: owner, repo, clientName.
list_pulls(page, repo, owner, state, per_page, clientName)- List pull requests for a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN. Required: owner, repo, clientName.
list_repos(org, page, type, per_page, clientName)- 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. Required: clientName.
list_tools(clientName)- Lists all available MCP servers and their tools in the workspace.
push_file(sha, path, repo, owner, branch, content, message, clientName)- 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. Required: owner, repo, path, content, branch, message, clientName.
read_mermaid_file(ref, path, repo, owner, clientName)- 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. Required: owner, repo, path, clientName.
search_mermaid_icons(limit, query, provider, clientName)- 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 suitable icons found, increase limit and retry. Supports AWS, Azure, GCP, and FontAwesome icon sets. Required: query, clientName.
update_notion_mermaid_diagram(code, blockId, caption, clientName)- Update the Mermaid source code (and optional caption) of an existing mermaid code block by its block ID. Required: blockId, code, clientName.
validate_and_render_mermaid_diagram(prompt, clientName, diagramType, mermaidCode, useUrlShortener)- 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 workflow. Required: prompt, mermaidCode, diagramType, clientName.
Last successful function declaration observed on . Source: https://mcp.mermaidchart.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.mermaidchart.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2025-09-18 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2025-09-18 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 25 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.mermaidchart.com | |
| mcp endpoint status | ok | The server listed 25 functions when asked. | as of probe | mcp.mermaidchart.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json