livediagram

io.github.livediagram-appPublished by GitHub account livediagram-appv0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server that lets an assistant create, edit, share and render real-time collaborative diagrams and mindmaps on livediagram.app.

What you can do
  • Create diagrams and mindmaps on livediagram.app
  • Edit existing diagrams and mindmaps
  • Share diagrams with collaborators
  • Render diagrams for viewing or output
  • Work within a real-time collaborative canvas
When to use it
Useful when you want an assistant to turn ideas, plans or structures into diagrams or mindmaps, or to update and share diagrams that already live on livediagram.app, without leaving the conversation.
Requirements
A remote MCP endpoint at mcp.livediagram.app over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your livediagram.app account. Creating, editing and sharing diagrams changes data in that account, and sharing exposes content to other people, so review what is created or shared before relying on it.

Installation

In SourceWeft

  1. Open livediagram in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.livediagram-app%2Flivediagram/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "livediagram": {
      "type": "http",
      "url": "https://mcp.livediagram.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 29, 2026

Score

70% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts