ADK-Rust
← MCP server registry
Data & contentPublic source

flowchart-mcp-server

32 MCP tools for authoring diagrams and exporting them to draw.io (diagrams.net mxGraph XML), Mermaid, Graphviz DOT, SVG, PDF, and JSON — plus Mermaid import. Multi-page documents, swimlanes & nested containers, rich…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

Provides flowchart capabilities through a typed MCP contract.

Architecture

How flowchart-mcp-server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

flowchart-mcp-server

Validates the request and owns 40 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: rmcp

This repository does not currently publish a dedicated architecture SVG. The integration diagram above is generated from its documented transport and server boundary; use the official README for implementation-specific details.

Tool catalog

What can an agent ask flowchart-mcp-server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

40 named tools

create_flowchart

Create a new flowchart (direction TB/BT/LR/RL, optional template). Returns a handle.

read only
list_templates

List available flowchart templates for create_flowchart.

read only
close_flowchart

Close a flowchart and free its memory.

read only
describe_flowchart

Describe a flowchart: direction, title, and full node/edge/subgraph listing with edge indexes.

read only
add_node

Add a node with a shape (13 presets) and optional fill/stroke/text_color/stroke_width.

read only
update_node

Update a node's label and/or shape.

read only
style_node

Set a node's visual style (fill/stroke/text_color/stroke_width, font, bold/italic, align, opacity, rounded, shadow, dashed).

read only
set_node_image

Set or clear a node's image (path or URI), rendering it as an image shape.

read only
set_node_stencil

Set or clear a node's draw.io stencil (catalog key like 'aws.ec2' or raw mxgraph.* token). Renders in the drawio export.

read only
list_stencils

List built-in draw.io stencils (AWS/Azure/GCP/network/Kubernetes/UML/BPMN/mockup), filterable by category and query.

read only
remove_node

Remove a node and every edge touching it.

read only
move_node

Manually place/size a node (x+y and/or w+h in canvas pixels), overriding auto-layout; clear returns it to auto.

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

37 read only3 local write
  • The registry manifest declares read only, local write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
rmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install flowchart-mcp-server
MCP client configuration
{
  "mcpServers": {
    "flowchart": {
      "command": "flowchart-mcp-server"
    }
  }
}

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.mdIssues and support ↗github.com issues

Keep exploring

More in data & content.

ADK Rust MCP ToolkitProduction-ready Model Context Protocol (MCP) servers for generative media, built in Rust. Generate images, videos, music, and speech through a unified, provider-agnostic interface.44 toolsArtifact Store MCP ServerGoverned artifact registry for ADK-Rust Enterprise agents. Content-immutable, versioned, provenance-linked, hash-verified artifacts with policy-driven lifecycle.15 toolsContent Management MCP ServerUnified content platform for AI agents — manage articles, social media, YouTube videos, media library, SEO, and publishing workflows from a single MCP server. 26 tools across content, social, and video.26 tools

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
0.1.0
License
Apache-2.0
Tools
40
Revision
32b8fb6eb321
Updated
Jun 6, 2026
Transportsstdio