Back to Browse

Livediagram MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Create, edit, share and render real-time collaborative diagrams and mindmaps on livediagram.app.

About

Create, edit, share and render real-time collaborative diagrams and mindmaps on livediagram.app.

Remote endpoints: streamable-http: https://mcp.livediagram.app/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-livediagram-app-livediagram": {
      "url": "https://mcp.livediagram.app/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

liveworkspace

The monorepo for liveworkspace and its products, livediagram, liveplanner, livedocuments and livedesign, plus what they share.

packages/        shared by every product (@liveworkspace/*)
liveworkspace/   the platform: the liveworkspace.app site, its services (accounts, index, drive, export,
                 media, community, telemetry, status), the migrate tool, and its specs (liveworkspace/docs/specs)
livediagram/     livediagram.app
liveplanner/     liveplanner.app
livedocuments/   livedocuments.app: articles, slides and infographics
livedesign/      livedesign.app: logos, wireframes and photos
livehuddle/      livehuddle.app: meetings and workshops, forked from livediagram in-tree
docs/            how this repo is laid out, CI and deploys, and the move from the historical livediagram.app

Read docs/structure.md first: it covers what's shared, what each product keeps, and the order the sharing was done in.

Every product and the platform keeps its specs and blueprints in its own docs/specs/ (liveworkspace's are liveworkspace/docs/specs). A change updates the spec first, then the blueprint, then the code.

Working in it

One pnpm workspace and one lockfile, at the root. Node 22+, pnpm via corepack.

corepack pnpm install
corepack pnpm dev:diagram        # livediagram's apps
corepack pnpm dev:planner        # liveplanner's apps
corepack pnpm dev:documents      # livedocuments' apps, on the 33xx ports
corepack pnpm dev:design         # livedesign's apps, on the 34xx ports
corepack pnpm dev:huddle         # livehuddle's apps, on the 35xx ports
corepack pnpm dev:workspace      # liveworkspace.app on :3000, with its seven services behind it
corepack pnpm dev:site           # liveworkspace.app's pages alone on :3000
corepack pnpm dev:accounts       # the accounts API alone on :8787
corepack pnpm dev:telemetry      # the telemetry API alone on :8790
corepack pnpm dev:community      # the Community API alone on :8791
corepack pnpm dev:media          # the media API alone on :8792
corepack pnpm dev:index          # the index API (One Explorer) alone on :8793
corepack pnpm dev:status         # the status Worker alone on :3010
corepack pnpm dev:drive          # the Google Drive mirror alone on :3011
corepack pnpm typecheck          # everything; or inside a product folder, just that product

Each product folder keeps its own scripts (cd livediagram && corepack pnpm test runs only livediagram's tests), its own docs, and its own AGENTS.md for product-specific rules. The lint, format, test and Next.js settings are shared (packages/oxlint-config, prettier-config, vitest-config, next-config), so a rule changes once for every product.

Security

Found a vulnerability in liveworkspace.app or any app? Please report it privately through GitHub's advisory form, never in a public issue. SECURITY.md has the policy, and the specs are in Vulnerability disclosure.

Deploys

Every product deploys from here, from the root .github/, to the liveworkspace Cloudflare account each wrangler.toml pins. Staging follows main, and production is a manual gate that ships what staging runs. A deploy builds and ships only the Workers a change reaches. The products' own .github/ folders are inert. docs/ci.md has the details.

Reviews

No reviews yet

Be the first to review this server!