Combien d'outils expose com.mermaidchart/mermaid-mcp ?

com.mermaidchart/mermaid-mcp expose 25 outil(s). Le coût de contexte pour les charger tous est d'environ 5954 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / com.mermaidchart/mermaid-mcp

com.mermaidchart/mermaid-mcp

serveur MCP (Model Context Protocol) · Mermaid Server 1.0.0

▸ Dev & Code

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

streamable-httpType / transport

configAccès

~5954 tokensCoût de contexte

25Outils

Est-ce que com.mermaidchart/mermaid-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.mermaidchart/mermaid-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 25 outils

create_issue≈ 201 tokens
Create an issue in a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN with issues write if creating issues in private repos.
Paramètres, retour & exemple (6)
Paramètres
- body · string · optionnel
  Issue body in markdown.
- repo · string · requis
- owner · string · requis
- title · string · requis
- labels · array · optionnel
  Label names (must already exist in the repository).
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "create_issue", "arguments": {"repo": "texte", "owner": "texte", "title": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
create_pr≈ 373 tokens
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).
Paramètres, retour & exemple (9)
Paramètres
- body · string · requis
  PR description (markdown).
- repo · string · requis
- files · array · requis
  Files to add or update.
- owner · string · requis
- title · string · requis
- baseBranch · string · optionnel
  Branch to base the PR on (e.g. main). Defaults to the repo default branch.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
- headBranch · string · requis
  Name of the new branch (must not already exist on the remote).
- commitMessage · string · requis
  Single commit message for the file changes.
Exemple d'appel
```
{"name": "create_pr", "arguments": {"body": "texte", "repo": "texte", "files": [], "owner": "texte", "title": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
generate_jira_kanban_board≈ 322 tokens
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.
Paramètres, retour & exemple (6)
Paramètres
- sprint · string · optionnel
  Filter by sprint name or numeric ID, e.g. 'Sprint 12' or '42'.
- assignee · string · optionnel
  Filter by assignee — Jira account ID, display name, or 'currentUser()'.
- issueType · string · optionnel
  Filter by issue type, e.g. 'Story', 'Bug', 'Task'.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
- maxResults · integer · optionnel
  Maximum number of issues to fetch (1–100, default 50).
- projectKey · string · requis
  REQUIRED: Jira project key, e.g. 'PROJ' or 'MYTEAM'.
Exemple d'appel
```
{"name": "generate_jira_kanban_board", "arguments": {"clientName": "texte", "projectKey": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
generate_ticket_dependency_tree≈ 534 tokens
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.
Paramètres, retour & exemple (11)
Paramètres
- sprint · string · optionnel
  Filter by sprint name or numeric ID, e.g. 'Sprint 12' or '42'.
- status · string · optionnel
  Filter by issue status, e.g. 'In Progress', 'To Do', 'Done'.
- assignee · string · optionnel
  Filter by assignee — Jira account ID, display name, or 'currentUser()'.
- reporter · string · optionnel
  Filter by reporter — Jira account ID or display name.
- colorMode · string · optionnel · light | dark | none
  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).
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
- maxResults · integer · optionnel
  Target number of issues to render in the tree (1–100, default 50).
- projectKey · string · requis
  REQUIRED: Jira project key, e.g. 'PROJ' or 'MYTEAM'. Used as the base JQL project filter.
- createdAfter · string · optionnel
  Include only issues created on or after this date, ISO format: '2024-01-15'.
- createdBefore · string · optionnel
  Include only issues created on or before this date, ISO format: '2024-03-31'.
- useUrlShortener · boolean · optionnel
  Shorten the preview/edit URL via Short.io. Disable to get the full unshortened URL (default true).
Exemple d'appel
```
{"name": "generate_ticket_dependency_tree", "arguments": {"clientName": "texte", "projectKey": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
generate_ticket_diagram≈ 283 tokens
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.
Paramètres, retour & exemple (3)
Paramètres
- colorMode · string · optionnel · light | dark | none
  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 · requis
  REQUIRED: Jira issue key, e.g. 'MC-123' or 'PROJ-42'.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "generate_ticket_diagram", "arguments": {"ticketKey": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
generate_ticket_timeline≈ 277 tokens
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.
Paramètres, retour & exemple (3)
Paramètres
- view · string · optionnel · state | timeline
  Diagram view to generate. 'state' shows status transitions; 'timeline' shows all field changes over time.
- ticketKey · string · requis
  REQUIRED: Jira issue key, e.g. 'MC-123' or 'PROJ-42'.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "generate_ticket_timeline", "arguments": {"ticketKey": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_diagram_summary≈ 222 tokens
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.
Paramètres, retour & exemple (3)
Paramètres
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
- contextHint · string · optionnel
  Optional: Context hint to help generate a more accurate summary.
- diagramContent · string · requis
  The Mermaid diagram content/code for which to generate a summary.
Exemple d'appel
```
{"name": "get_diagram_summary", "arguments": {"clientName": "texte", "diagramContent": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_diagram_title≈ 252 tokens
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.
Paramètres, retour & exemple (4)
Paramètres
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
- diagramType · string · optionnel
  Optional: The type of Mermaid diagram (e.g., 'flowchart', 'sequenceDiagram', 'gantt') for better context in title generation.
- currentTitle · string · optionnel
  Optional: The current title of the diagram, if any, for context.
- diagramContent · string · requis
  The Mermaid diagram content/code for which to generate a title.
Exemple d'appel
```
{"name": "get_diagram_title", "arguments": {"clientName": "texte", "diagramContent": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_issue_comments≈ 224 tokens
List comments on an issue by issue number. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN.
Paramètres, retour & exemple (6)
Paramètres
- page · integer · optionnel
- repo · string · requis
- owner · string · requis
- per_page · integer · optionnel
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
- issue_number · integer · requis
  Issue number (not a PR number unless the PR is also addressed as an issue on GitHub).
Exemple d'appel
```
{"name": "get_issue_comments", "arguments": {"repo": "texte", "owner": "texte", "clientName": "texte", "issue_number": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_mermaid_syntax_document≈ 223 tokens
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.
Paramètres, retour & exemple (2)
Paramètres
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
- diagramType · string · requis
  The type of Mermaid diagram to get syntax documentation for (e.g., 'flowchart', 'sequenceDiagram', 'architecture-beta', 'gantt', 'gitgraph', 'classDiagram', 'stateDiagram', etc.).
Exemple d'appel
```
{"name": "get_mermaid_syntax_document", "arguments": {"clientName": "texte", "diagramType": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_notion_mermaid_diagram_by_block_id≈ 158 tokens
Retrieve a single Mermaid diagram block by its block ID. Returns the diagram code and optional caption.
Paramètres, retour & exemple (2)
Paramètres
- blockId · string · requis
  The Notion block ID of the mermaid code block (e.g. from get_notion_page_mermaid_diagrams).
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "get_notion_mermaid_diagram_by_block_id", "arguments": {"blockId": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_notion_page_mermaid_diagrams≈ 160 tokens
Extract all Mermaid code blocks from a Notion page. Returns block ID, diagram code, and optional caption for each block.
Paramètres, retour & exemple (2)
Paramètres
- pageUrl · string · requis
  URL of the Notion page (e.g. https://www.notion.so/My-Page-abc123...).
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "get_notion_page_mermaid_diagrams", "arguments": {"pageUrl": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
get_pull_comments≈ 232 tokens
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.
Paramètres, retour & exemple (6)
Paramètres
- page · integer · optionnel
- repo · string · requis
- owner · string · requis
- per_page · integer · optionnel
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
- pull_number · integer · requis
  Pull request number.
Exemple d'appel
```
{"name": "get_pull_comments", "arguments": {"repo": "texte", "owner": "texte", "clientName": "texte", "pull_number": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
insert_notion_mermaid_diagram≈ 197 tokens
Append a Mermaid diagram as a code block to a Notion page. The block is added at the end of the page content.
Paramètres, retour & exemple (4)
Paramètres
- code · string · requis
  Mermaid diagram source code.
- caption · string · optionnel
  Optional caption displayed below the code block.
- pageUrl · string · requis
  URL of the Notion page to insert the diagram into.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "insert_notion_mermaid_diagram", "arguments": {"code": "texte", "pageUrl": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_branches≈ 236 tokens
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.
Paramètres, retour & exemple (4)
Paramètres
- repo · string · requis
- owner · string · requis
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
- branch_name · string · optionnel
  Exact branch name. When non-empty, returns that branch only. Omit to fetch the first 100 branches only.
Exemple d'appel
```
{"name": "list_branches", "arguments": {"repo": "texte", "owner": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_issues≈ 288 tokens
List issues for a repository (excludes pull requests). REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN.
Paramètres, retour & exemple (10)
Paramètres
- page · integer · optionnel
- repo · string · requis
- sort · string · optionnel · created | updated | comments
- owner · string · requis
- since · string · optionnel
  ISO 8601: only issues updated at or after this time.
- state · string · optionnel · open | closed | all
- labels · string · optionnel
  Comma-separated label names (GitHub API format).
- per_page · integer · optionnel
- direction · string · optionnel · asc | desc
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "list_issues", "arguments": {"repo": "texte", "owner": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_mermaid_files≈ 200 tokens
List .mmd Mermaid files in a GitHub repository (code search with tree fallback). REQUIRES: `Github-Token` header (HTTP) or GITHUB_TOKEN / GH_TOKEN.
Paramètres, retour & exemple (4)
Paramètres
- ref · string · optionnel
  Optional branch, tag, or commit for tree fallback when code search is unavailable.
- repo · string · requis
  Repository name.
- owner · string · requis
  Repository owner (user or organization).
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "list_mermaid_files", "arguments": {"repo": "texte", "owner": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_pulls≈ 193 tokens
List pull requests for a GitHub repository. REQUIRES: `Github-Token` (HTTP) or GITHUB_TOKEN / GH_TOKEN.
Paramètres, retour & exemple (6)
Paramètres
- page · integer · optionnel
- repo · string · requis
- owner · string · requis
- state · string · optionnel · open | closed | all
- per_page · integer · optionnel
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "list_pulls", "arguments": {"repo": "texte", "owner": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_repos≈ 258 tokens
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.
Paramètres, retour & exemple (5)
Paramètres
- org · string · optionnel
  Optional: organization login. If set, lists that org's repositories; otherwise lists repos for the authenticated user.
- page · integer · optionnel
- type · string · optionnel · all | owner | member | public | private
  User repo filter; ignored when `org` is set.
- per_page · integer · optionnel
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "list_repos", "arguments": {"clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
list_tools≈ 111 tokens
Lists all available MCP servers and their tools in the workspace.
Paramètres, retour & exemple (1)
Paramètres
- clientName · string · optionnel
  OPTIONAL: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
Exemple d'appel
```
{"name": "list_tools", "arguments": {"clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
push_file≈ 240 tokens
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.
Paramètres, retour & exemple (8)
Paramètres
- sha · string · optionnel
  Existing blob SHA to update; omit to create or to let the service detect.
- path · string · requis
- repo · string · requis
- owner · string · requis
- branch · string · requis
  Branch to commit to.
- content · string · requis
  Full file content.
- message · string · requis
  Commit message.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "push_file", "arguments": {"path": "texte", "repo": "texte", "owner": "texte", "branch": "texte", "content": "texte", "message": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
read_mermaid_file≈ 199 tokens
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.
Paramètres, retour & exemple (5)
Paramètres
- ref · string · optionnel
  Optional: branch, tag, or commit SHA; defaults to the default branch.
- path · string · requis
  Path to the .mmd file in the repository.
- repo · string · requis
- owner · string · requis
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "read_mermaid_file", "arguments": {"path": "texte", "repo": "texte", "owner": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
search_mermaid_icons≈ 317 tokens
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.
Paramètres, retour & exemple (4)
Paramètres
- limit · number · optionnel
  Optional: Maximum number of results to return per provider. Defaults to 10 for performance. Increase if needed.
- query · string · requis
  Search query for icons (e.g., 'aws', 'azure', 'gcp', 'fa', 'lambda', 's3', 'database'). Use specific terms for better results.
- provider · string · optionnel
  Optional: Filter by specific provider ('aws', 'azure', 'gcp', 'fa'). If not provided, searches all providers.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
Exemple d'appel
```
{"name": "search_mermaid_icons", "arguments": {"query": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
update_notion_mermaid_diagram≈ 196 tokens
Update the Mermaid source code (and optional caption) of an existing mermaid code block by its block ID.
Paramètres, retour & exemple (4)
Paramètres
- code · string · requis
  New Mermaid diagram source code.
- blockId · string · requis
  The Notion block ID of the mermaid code block to update.
- caption · string · optionnel
  Optional new caption. Omit to clear the existing caption.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server for analytics tracking.
Exemple d'appel
```
{"name": "update_notion_mermaid_diagram", "arguments": {"code": "texte", "blockId": "texte", "clientName": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
validate_and_render_mermaid_diagram≈ 326 tokens
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.
Paramètres, retour & exemple (5)
Paramètres
- prompt · string · requis
  A text description of the diagram to generate.
- clientName · string · requis
  REQUIRED: The name of the client/agent using the MCP server (e.g., 'claude', 'cursor', 'vscode', 'chatgpt', 'copilot') for analytics tracking.
- diagramType · string · requis
  The type of Mermaid diagram (e.g., 'flowchart', 'sequenceDiagram', 'gantt').
- mermaidCode · string · requis
  Mermaid code to render. Mermaid validates automatically during rendering - if invalid, tool returns error details for fixing.
- useUrlShortener · boolean · optionnel
  Whether to use URL shortening for the Mermaid link. Defaults to true, set to false to disable shortening.
Exemple d'appel
```
{"name": "validate_and_render_mermaid_diagram", "arguments": {"prompt": "texte", "clientName": "texte", "diagramType": "texte", "mermaidCode": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.mermaidchart.com/mcp