Skip to main content
Glama

Server Details

Generate cloud architecture diagrams, flowcharts, and sequence diagrams.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
ByteOverDev/diagrams-mcp
GitHub Stars
3
Server Listing
diagrams-mcp

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 4.5/5 across 9 of 9 tools scored. Lowest: 3.7/5.

Server CoherenceA
Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. The tools are well-separated into equivalence mapping (find_equivalent, list_categories), node browsing (list_providers, list_services, list_nodes, search_nodes), and diagram rendering (render_diagram, render_mermaid, render_plantuml). The descriptions clearly differentiate their functions, and there's no overlap in what they accomplish.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern using snake_case throughout. The verbs are appropriate and descriptive: 'find', 'list', 'render', and 'search' clearly indicate the action, while nouns like 'equivalent', 'categories', 'diagram', etc., specify the target. There are no deviations in naming conventions across the toolset.

Tool Count5/5

With 9 tools, the count is well-scoped for a diagrams server covering equivalence mapping, node discovery, and multiple rendering backends. Each tool earns its place by addressing a specific need in the workflow, from exploring available nodes to generating diagrams in different formats, without being overly sparse or bloated.

Completeness5/5

The tool surface is complete for the domain of diagram generation and node management. It covers the full lifecycle: discovering nodes (list_providers, list_services, list_nodes, search_nodes), understanding equivalences (find_equivalent, list_categories), and rendering diagrams in multiple formats (render_diagram, render_mermaid, render_plantuml). There are no obvious gaps, and the tools work together seamlessly as described.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.