mcp-server-diagramai

Created By
PadsterH2012a year ago
Overview

what is mcp-server-diagramai?

The mcp-server-diagramai is an implementation for integrating with DiagramAI, allowing AI agents to create, read, edit, and delete diagrams in real-time.

how to use mcp-server-diagramai?

To use mcp-server-diagramai, install it via npm or clone the repository from GitHub. Configure the API key and URL in your environment variables or configuration file, and then run the server to manage diagrams.

key features of mcp-server-diagramai?

  • Real-time access to diagram states and project structures.
  • Tools for creating, retrieving, updating, and deleting diagrams.
  • Project-based organization of diagrams.

use cases of mcp-server-diagramai?

  1. Collaborative diagram creation and editing in real-time.
  2. Integration with AI agents for automated diagram management.
  3. Organizing and managing multiple diagrams within projects.

FAQ from mcp-server-diagramai?

  • How do I install mcp-server-diagramai?

You can install it using npm with the command npm install -g mcp-server-diagramai or clone the repository from GitHub.

  • What permissions are required for the API key?

The API key must have permissions for creating, reading, updating, and deleting diagrams, as well as accessing project information.

  • What should I do if I encounter connection issues?

Ensure that the DiagramAI instance is running and accessible, and verify your API URL and key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PadsterH2012
Star
0
Language
TypeScript
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