com.mermaidchart/mermaid-mcp

REMOTE · MCP.MERMAIDCHART.COM · 2 COMPONENTS · SCANNED AUG 3

MCP server for Mermaid diagram validation and rendering

Available components

remote · mcp.mermaidchart.com 63 remote · mcp.mermaidchart.com 56

+1 this week 56 56 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 25 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability40

Verified sse transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability57

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 3828 tokens (~153/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage91

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
72% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.mermaidchart.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-mermaidchart-mermaid-mcp https://mcp.mermaidchart.com/sse

# ~/.codex/config.toml

[mcp_servers.com-mermaidchart-mermaid-mcp]
url = "https://mcp.mermaidchart.com/sse"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mermaidchart-mermaid-mcp": {
      "type": "remote",
      "url": "https://mcp.mermaidchart.com/sse",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-mermaidchart-mermaid-mcp --url https://mcp.mermaidchart.com/sse --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-mermaidchart-mermaid-mcp:
    url: "https://mcp.mermaidchart.com/sse"

// mcp.json

{
  "mcpServers": {
    "com-mermaidchart-mermaid-mcp": {
      "type": "http",
      "url": "https://mcp.mermaidchart.com/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 54

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.mermaidchart.com/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.mcp-prod.mdct.co	CN=Amazon RSA 2048 M01,O=Amazon,C=US	6 Mar 2026	19 Sept 2026	RSA 2048	SHA256-RSA	2e312666e00b01f8311e80099a05f2c
SANs: *.mcp-prod.mdct.co, mcp2.mermaidchart.com, mcp.mermaidchart.com, mcp.mermaid.ai
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA)	CN=Amazon Root CA 1,O=Amazon,C=US	23 Aug 2022	23 Aug 2030	RSA 2048	SHA256-RSA	77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA)	CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US	25 May 2015	31 Dec 2037	RSA 2048	SHA256-RSA	67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

DNSSEC insecure

Validation of mcp.mermaidchart.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
mermaidchart.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	404

Header	Value
content-security-policy	default-src 'none'
x-content-type-options	nosniff

Transports 2 probes

Transport	URL	Outcome	Status	Location
sse	https://mcp.mermaidchart.com/sse	Verified	200
http (plaintext)	http://mcp.mermaidchart.com/sse	HTTPS enforced	301	https://mcp.mermaidchart.com:443/sse

MCP tools — 25 exposed · ~3,828 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

create_issue ~115

Create an issue in a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN with issues write if creating issues in private repos.

Input Output Examples

Name	Type	Req	Description
body	string	—	Issue body in markdown.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
labels	array	—	Label names (must already exist in the repository).
owner	string	yes	—
repo	string	yes	—
title	string	yes	—

No output schema declared.

No examples provided.

create_pr ~203

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).

Input Output Examples

Name	Type	Req	Description
baseBranch	string	—	Branch to base the PR on (e.g. main). Defaults to the repo default branch.
body	string	yes	PR description (markdown).
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
commitMessage	string	yes	Single commit message for the file changes.
files	array	yes	Files to add or update.
headBranch	string	yes	Name of the new branch (must not already exist on the remote).
owner	string	yes	—
repo	string	yes	—
title	string	yes	—

No output schema declared.

No examples provided.

generate_jira_kanban_board ~215

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.

Input Output Examples

Name	Type	Req	Description
assignee	string	—	Filter by assignee — Jira account ID, display name, or 'currentUser()'.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
issueType	string	—	Filter by issue type, e.g. 'Story', 'Bug', 'Task'.
maxResults	integer	—	Maximum number of issues to fetch (1–100, default 50).
projectKey	string	yes	REQUIRED: Jira project key, e.g. 'PROJ' or 'MYTEAM'.
sprint	string	—	Filter by sprint name or numeric ID, e.g. 'Sprint 12' or '42'.

No output schema declared.

No examples provided.

generate_ticket_dependency_tree ~371

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.

Input Output Examples

Name	Type	Req	Description
assignee	string	—	Filter by assignee — Jira account ID, display name, or 'currentUser()'.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
colorMode	string	—	Color scheme for the diagram: 'light' (default pastel fills), 'dark' (deep fills for dark backgrounds), or 'none' (no fill/stroke overrides, inherits the Mermaid theme).
createdAfter	string	—	Include only issues created on or after this date, ISO format: '2024-01-15'.
createdBefore	string	—	Include only issues created on or before this date, ISO format: '2024-03-31'.
maxResults	integer	—	Target number of issues to render in the tree (1–100, default 50).
projectKey	string	yes	REQUIRED: Jira project key, e.g. 'PROJ' or 'MYTEAM'. Used as the base JQL project filter.
reporter	string	—	Filter by reporter — Jira account ID or display name.
sprint	string	—	Filter by sprint name or numeric ID, e.g. 'Sprint 12' or '42'.
status	string	—	Filter by issue status, e.g. 'In Progress', 'To Do', 'Done'.
useUrlShortener	boolean	—	Shorten the preview/edit URL via Short.io. Disable to get the full unshortened URL (default true).

No output schema declared.

No examples provided.

generate_ticket_diagram ~185

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
colorMode	string	—	Color scheme for the diagram: 'light' (default pastel fills), 'dark' (deep fills for dark backgrounds), or 'none' (no fill/stroke overrides, inherits the Mermaid theme).
ticketKey	string	yes	REQUIRED: Jira issue key, e.g. 'MC-123' or 'PROJ-42'.

No output schema declared.

No examples provided.

generate_ticket_timeline ~166

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
ticketKey	string	yes	REQUIRED: Jira issue key, e.g. 'MC-123' or 'PROJ-42'.
view	string	—	Diagram view to generate. 'state' shows status transitions; 'timeline' shows all field changes over time.

No output schema declared.

No examples provided.

get_diagram_summary ~139

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
contextHint	string	—	Optional: Context hint to help generate a more accurate summary.
diagramContent	string	yes	The Mermaid diagram content/code for which to generate a summary.

No output schema declared.

No examples provided.

get_diagram_title ~163

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
currentTitle	string	—	Optional: The current title of the diagram, if any, for context.
diagramContent	string	yes	The Mermaid diagram content/code for which to generate a title.
diagramType	string	—	Optional: The type of Mermaid diagram (e.g., 'flowchart', 'sequenceDiagram', 'gantt') for better context in title generation.

No output schema declared.

No examples provided.

get_issue_comments ~118

List comments on an issue by issue number. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
issue_number	integer	yes	Issue number (not a PR number unless the PR is also addressed as an issue on GitHub).
owner	string	yes	—
page	integer	—	—
per_page	integer	—	—
repo	string	yes	—

No output schema declared.

No examples provided.

get_mermaid_syntax_document ~145

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
diagramType	string	yes	The type of Mermaid diagram to get syntax documentation for (e.g., 'flowchart', 'sequenceDiagram', 'architecture-beta', 'gantt', 'gitgraph', 'classDiagram', 'stateDiagram', etc.).

No output schema declared.

No examples provided.

get_notion_mermaid_diagram_by_block_id ~91

Retrieve a single Mermaid diagram block by its block ID. Returns the diagram code and optional caption.

Input Output Examples

Name	Type	Req	Description
blockId	string	yes	The Notion block ID of the mermaid code block (e.g. from get_notion_page_mermaid_diagrams).
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.

No output schema declared.

No examples provided.

get_notion_page_mermaid_diagrams ~94

Extract all Mermaid code blocks from a Notion page. Returns block ID, diagram code, and optional caption for each block.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
pageUrl	string	yes	URL of the Notion page (e.g. https://www.notion.so/My-Page-abc123...).

No output schema declared.

No examples provided.

get_pull_comments ~127

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
owner	string	yes	—
page	integer	—	—
per_page	integer	—	—
pull_number	integer	yes	Pull request number.
repo	string	yes	—

No output schema declared.

No examples provided.

insert_notion_mermaid_diagram ~107

Append a Mermaid diagram as a code block to a Notion page. The block is added at the end of the page content.

Input Output Examples

Name	Type	Req	Description
caption	string	—	Optional caption displayed below the code block.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
code	string	yes	Mermaid diagram source code.
pageUrl	string	yes	URL of the Notion page to insert the diagram into.

No output schema declared.

No examples provided.

list_branches ~183

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.

Input Output Examples

Name	Type	Req	Description
branch_name	string	—	Exact branch name. When non-empty, returns that branch only. Omit to fetch the first 100 branches only.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
owner	string	yes	—
repo	string	yes	—

No output schema declared.

No examples provided.

list_issues ~151

List issues for a repository (excludes pull requests). REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
direction	string	—	—
labels	string	—	Comma-separated label names (GitHub API format).
owner	string	yes	—
page	integer	—	—
per_page	integer	—	—
repo	string	yes	—
since	string	—	ISO 8601: only issues updated at or after this time.
sort	string	—	—
state	string	—	—

No output schema declared.

No examples provided.

list_mermaid_files ~117

List .mmd Mermaid files in a GitHub repository (code search with tree fallback). REQUIRES: `Github-Token` header (HTTP) or GITHUB_TOKEN / GH_TOKEN.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
owner	string	yes	Repository owner (user or organization).
ref	string	—	Optional branch, tag, or commit for tree fallback when code search is unavailable.
repo	string	yes	Repository name.

No output schema declared.

No examples provided.

list_pulls ~98

List pull requests for a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
owner	string	yes	—
page	integer	—	—
per_page	integer	—	—
repo	string	yes	—
state	string	—	—

No output schema declared.

No examples provided.

list_repos ~143

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
org	string	—	Optional: organization login. If set, lists that org's repositories; otherwise lists repos for the authenticated user.
page	integer	—	—
per_page	integer	—	—
type	string	—	User repo filter; ignored when `org` is set.

No output schema declared.

No examples provided.

list_tools ~68

Lists all available MCP servers and their tools in the workspace.

Input Output Examples

Name	Type	Req	Description
clientName	string	—	OPTIONAL: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.

No output schema declared.

No examples provided.

push_file ~142

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.

Input Output Examples

Name	Type	Req	Description
branch	string	yes	Branch to commit to.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
content	string	yes	Full file content.
message	string	yes	Commit message.
owner	string	yes	—
path	string	yes	—
repo	string	yes	—
sha	string	—	Existing blob SHA to update; omit to create or to let the service detect.

No output schema declared.

No examples provided.

read_mermaid_file ~131

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
owner	string	yes	—
path	string	yes	Path to the .mmd file in the repository.
ref	string	—	Optional: branch, tag, or commit SHA; defaults to the default branch.
repo	string	yes	—

No output schema declared.

No examples provided.

search_mermaid_icons ~238

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
limit	number	—	Optional: Maximum number of results to return per provider. Defaults to 10 for performance. Increase if needed.
provider	string	—	Optional: Filter by specific provider ('aws', 'azure', 'gcp', 'fa'). If not provided, searches all providers.
query	string	yes	Search query for icons (e.g., 'aws', 'azure', 'gcp', 'fa', 'lambda', 's3', 'database'). Use specific terms for better results.

No output schema declared.

No examples provided.

update_notion_mermaid_diagram ~110

Update the Mermaid source code (and optional caption) of an existing mermaid code block by its block ID.

Input Output Examples

Name	Type	Req	Description
blockId	string	yes	The Notion block ID of the mermaid code block to update.
caption	string	—	Optional new caption. Omit to clear the existing caption.
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
code	string	yes	New Mermaid diagram source code.

No output schema declared.

No examples provided.

validate_and_render_mermaid_diagram ~208

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.

Input Output Examples

Name	Type	Req	Description
clientName	string	yes	REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
diagramType	string	yes	The type of Mermaid diagram (e.g., 'flowchart', 'sequenceDiagram', 'gantt').
mermaidCode	string	yes	Mermaid code to render. Mermaid validates automatically during rendering - if invalid, tool returns error details for fixing.
prompt	string	yes	A text description of the diagram to generate.
useUrlShortener	boolean	—	Whether to use URL shortening for the Mermaid link. Defaults to true, set to false to disable shortening.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	54
27 Jul	55
28 Jul	55
29 Jul	56
30 Jul	54
31 Jul	55
1 Aug	55
2 Aug	56
3 Aug	56