Ilograph MCP Server

Created By
QuincyMillerDeva year ago
Overview

What is Ilograph MCP Server?

Ilograph MCP Server is a comprehensive Model Context Protocol (MCP) server designed for automated Ilograph diagram generation from various codebases. It analyzes source code across multiple programming languages and generates native .ilograph files that can be opened directly in the Ilograph editor, with optional rendering via the Ilograph Export API.

How to use Ilograph MCP Server?

To use the Ilograph MCP Server, you can either run it locally using Python or deploy it using Docker. After setting up, you can analyze your codebase by executing specific commands to generate .ilograph files or render diagrams in various formats.

Key features of Ilograph MCP Server?

  • Native .ilograph file generation for direct use in Ilograph editor.
  • Multi-language support for Python, JavaScript/TypeScript, and Java.
  • Compliance with MCP protocol for integration with AI assistants.
  • Optional export to SVG, PNG, HTML, or PDF formats.
  • Ability to generate diagrams from different architectural perspectives.
  • Containerized deployment with Docker support.
  • Production-ready with comprehensive logging and monitoring.
  • Extensible architecture for easy addition of new languages and features.

Use cases of Ilograph MCP Server?

  1. Automating the generation of architecture diagrams from existing codebases.
  2. Supporting software development teams in visualizing code structure and dependencies.
  3. Enhancing documentation processes by providing visual representations of code architecture.

FAQ from Ilograph MCP Server?

  • What programming languages does it support?

It supports Python, JavaScript/TypeScript, and Java.

  • Is Docker required to run the server?

No, Docker is optional; you can run it directly with Python.

  • Can I generate diagrams in formats other than .ilograph?

Yes, you can render diagrams as SVG, PNG, HTML, or PDF using the Ilograph Export API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
QuincyMillerDev
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago