# Lucid MCP MCP Server

> **Lucid MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Lucid MCP.
>
> MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows,
> token refresh, and production-grade auto-scaling — so your AI agents can connect to
> third-party services and run freely without you managing any MCP server yourself.
>
> Server page:  https://mewcp.com/mcp/lucid-mcp
> MewCP docs:   https://docs.mewcp.com
> Full catalog: https://mewcp.com/llms.txt

---

## About

Create and manage Lucid diagrams with AI agents, including flowcharts, process maps, architecture diagrams, and visual documentation. Search existing Lucid content and update diagrams using natural language.

---

## Details

- Server ID: `lucid-mcp`
- Version: 1.0.0
- Tools: 38
- Authentication: OAuth, managed by MewCP
- Transport: http

---

## Access

The gateway URL below serves your **entire MewCP toolset**, not this server on its
own. Pasting a config snippet is not enough — Lucid MCP has to be in the toolset
first. In order:

1. Add Lucid MCP to your toolset at https://mewcp.com/mcp/lucid-mcp
2. Connect your Lucid MCP account (OAuth); MewCP stores the credential and attaches it to each call
3. Copy your MewCP API key from the dashboard (Developer)
4. Configure your client with the snippet for it below

Once connected, an agent does **not** see this server's tools as top-level tools.
It sees four meta-tools and reaches everything through them:

- `search(query)` — find tools by keyword across the toolset
- `get_schema(tools)` — full description and arguments for the tools you picked
- `list_accounts(provider)` — only when one app has several connected accounts
- `call_tool(server_maskedId, tool_name, args)` — execute

So the list below is what `search` can return for this server, not a set of
callable tool names on their own.

---

## Tools (38)

Descriptions are truncated to 160 characters; call `get_schema`
for the full text and the argument schema. Where a tool is annotated, its type
is shown — treat `destructive` as irreversible.

- `lucid_copy_document_style` _(read)_ — Read a Lucid document's visual style to use when creating diagrams. Use when the user asks to match or copy the style of an existing document. Returns a…
- `get_mcp_resource` _(read)_ — Reads a resource from this MCP server by URI. When a tool description says to read a resource (e.g. "read lucid://skills/diagram-specification"), use this tool…
- `search` _(read)_ — Search the user's Lucid account for documents by title/keyword. This is the default tool for a generic "search for X" request. Use it unless the user…
- `fetch` _(read)_ — Retrieves the structured content of a specific Lucid document by its ID. Returns document content organized by pages, each containing spatial regions of…
- `lucid_search_document` _(read)_ — Locates regions of a Lucid document that contain specific text. Use this BEFORE `fetch` when you're looking for content you can describe with specific words or…
- `lucid_create_document_share_link` _(write)_ — Creates a new share link for a document with specified permissions. Args: document_id: Valid UUID of the document to share role: Access permission level - one…
- `share_document_with_collaborators` _(write)_ — Share a Lucid document with collaborators by granting them access. This tool searches for users by their email addresses, then grants them the specified…
- `lucid_create_org_chart` _(write)_ — Creates a Lucidchart document containing an org chart from structured node data. Use this tool when the user wants to create an organizational chart, team…
- `lucid_list_integrations` _(read)_ — List the user's available card integrations and their connection status. Use this to find out which third-party integrations (e.g. Jira) the user is connected…
- `lucid_import_integration_cards` _(write)_ — Import records from a third-party integration as linked cards. You MUST call `lucid_list_integrations` first to obtain `instance_id` — it is the exact…
- `lucid_create_diagram_from_specification` _(write)_ — Creates a Lucid document using the Standard Import format (.lucid file). When the user requests a diagram without explicitly asking for Mermaid or a diagram…
- `lucid_validate_diagram_specification` _(read)_ — Check Standard Import JSON for layout problems before creating a document. Runs the GEOMETRY AND TEXT PREFLIGHT rules from lucid://diagram-specification over…
- `lucid_create_diagram_from_mermaid` _(write)_ — Creates a Lucid document from existing Mermaid code at the user's request. STOP. Read this ENTIRE description before calling. The rules below are load-bearing…
- `lucid_create_mind_map` _(write)_ — Creates a Lucid document containing a mind map from structured node data. Use this tool when the user wants to create a mind map or hierarchical topic diagram.…
- `lucid_create_sequence_diagram` _(write)_ — Creates a Lucid document containing a UML sequence diagram from PlantUML markup. REQUIREMENT: Before attempting to use this tool, you MUST read the resource at…
- `lucid_create_erd` _(write)_ — Creates a Lucid document containing a data-backed Entity Relationship Diagram (ERD). Use this tool when the user wants to create an ERD / database schema…
- `_lucid_create_embed` _(write)_ — Internal tool for MCP Apps extension only. Creates an embed for a Lucid document, returning an embed ID.
- `_lucid_create_embed_session_token` _(write)_ — Internal tool for MCP Apps extension only. Creates a session token for an existing embed, returning a token and embed URL.
- `lucid_export_document_as_PNG` _(read)_ — Exports a Lucid document page as a PNG image. To crop the image, pass a bounding_box whose x, y, w, and h fields correspond directly to BoundingBox values…
- `lucid_fetch_item_image` _(read)_ — Fetches the source image attached to a specific item in a Lucid document.
- `lucid_add_block` _(write)_ — Add a new block (shape) to a Lucid document. DISCOVERY: Use lucid_shape_library to find valid block_type values for the target document, and…
- `lucid_add_dynamic_table` _(write)_ — Add a dynamic table to a Lucid document. Dynamic tables organize items into rows and columns and can be used for matrices, grids, kanban-style boards, planning…
- `lucid_add_items_to_dynamic_table` _(write)_ — Add existing canvas blocks to a dynamic table. The generator's grouping logic places each block in the correct row/column based on its pivot-field value.…
- `lucid_shape_library` _(read)_ — Discover shapes/blocks available to INSERT into a Lucid document. This does NOT find documents or text inside a document. To find a document by name use…
- `lucid_shape_details` _(read)_ — Get default size, colors, and advanced/text-area properties for one or more shape classes. Use this tool after lucid_shape_library has narrowed to candidate…
- `lucid_edit_dynamic_table_metadata` _(destructive)_ — Edit the metadata/settings of an existing dynamic table. Updates the reactive settings of a dynamic-table generator: the agile capacity-planning and…
- `lucid_add_line` _(write)_ — Add a new line to a Lucid document, connecting two points or shapes. Each endpoint is either: - A position endpoint: provide endpoint_x and endpoint_y…
- `lucid_delete_items` _(destructive)_ — Delete one or more blocks or lines from a Lucid document. This action is destructive and cannot be undone via the API. Use the fetch tool first to get item IDs…
- `lucid_edit_item` _(destructive)_ — Edit an existing block or line in a Lucid document. Use the fetch tool first to get item IDs from the document. For blocks: use x, y, width, height to…
- `list_document_threads` _(read)_ — List collaboration threads on a Lucid document. Args: document_id: The UUID of the document. Returns: JSON string of the Lucid API response (array of thread…
- `list_document_thread_comments` _(read)_ — List comments on a specific collaboration thread of a Lucid document. Args: document_id: The UUID of the document. thread_id: The ID of the thread whose…
- `post_document_thread_comment` _(write)_ — Post a new comment to an existing thread on a Lucid document. Args: document_id: The UUID of the document. thread_id: The thread to comment on. content: The…
- `lucid_submit_feedback` _(write)_ — Submits user feedback about the Lucid MCP server to the product team. Use this tool when the user wants to share feedback, report a bug, request a feature, or…
- `lucid_get_document_metadata` _(read)_ — Get metadata for a Lucid document. The requesting user must have at least read-only access to the document. Owner information is returned for unpublished…
- `lucid_update_document` _(destructive)_ — Update a Lucid document's title, parent folder, or custom tags. Use this tool to rename a document or move it between folders. At least one of `title`,…
- `lucid_create_folder` _(write)_ — Create a new folder in the user's Lucid account. Args: name: Folder name (1-300 characters, no leading/trailing whitespace). folder_type: Either "folder"…
- `lucid_update_folder` _(destructive)_ — Rename a Lucid folder or move it to a different parent. At least one of `name` or `parent` must be provided. Args: folder_id: Numeric ID of the folder to…
- `lucid_list_folder_contents` _(read)_ — List the documents and subfolders inside a Lucid folder. Pass `folder_id=None` (the default) to list the user's root folder. When more pages are available, the…

---

## Connect

Gateway URL: https://gateway.mewcp.com/personal/mcp

Every request carries one header:

    Authorization: Bearer <API_KEY>

Replace `API_KEY` with your own key from the dashboard (Developer).

## Apps

### Claude Desktop

Mac & Windows app

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization: Bearer API_KEY"
      ]
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open Claude Desktop → Settings → Developer → "Edit Config"
2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
3. Save the file and restart Claude Desktop
4. Start a new conversation — your tool will be available

### VS Code

Copilot / Cline

- Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead.

```json
{
  "mcp.servers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have a "servers" section in your mcp.json? Just add the server entry inside it.

1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
2. Run "MCP: Open User Configuration" to open your mcp.json
3. Paste the snippet and save
4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat

### Cursor

AI-first editor

- macOS: `~/.cursor/mcp.json`
- Windows: `%USERPROFILE%\.cursor\mcp.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it.

1. Open Cursor → Settings → Cursor Settings → MCP
2. Click "Add new global MCP server"
3. Paste the snippet and save
4. Restart Cursor

### Codex

OpenAI's CLI agent

- Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers.

1. Open your Codex MCP config or project-level config file
2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects
3. Save the file and restart Codex
4. Verify the tool is available inside a fresh session

### Claude Code

Anthropic's CLI agent

- ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file and start (or restart) Claude Code
4. Or skip the file entirely and run the CLI command below instead

### OpenCode

Open-source terminal agent

- ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist.

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mewcp": {
      "type": "remote",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcp" section in your opencode.json? Just add the server entry inside it.

1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and start (or restart) OpenCode

### OpenClaw

Self-hosted agent gateway

- ~/.openclaw/openclaw.json — create it if it doesn't exist.

```json
{
  "mcp": {
    "servers": {
      "mewcp": {
        "transport": "streamable-http",
        "url": "https://gateway.mewcp.com/personal/mcp",
        "enabled": true,
        "headers": {
          "Authorization": "Bearer API_KEY"
        }
      }
    }
  }
}
```

Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers".

1. Open ~/.openclaw/openclaw.json in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and restart OpenClaw

### Antigravity

Google's agentic IDE

- ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist.

```json
{
  "mcpServers": {
    "mewcp": {
      "serverUrl": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported.

1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager)
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file — the server connects automatically

### Hermes

Nous Research's CLI agent

- config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key.

```yaml
mcp_servers:
  mewcp:
    url: "https://gateway.mewcp.com/personal/mcp"
    headers:
      Authorization: "Bearer API_KEY"
```

Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it.

1. Open config.yaml in your Hermes config directory
2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any)
3. Save the file, then run /reload-mcp in Hermes (or start a fresh session)
4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected

### DeepSeek Harness

DeepSeek's agent harness

- cordis.yml in your DSH project — or the patch file you mount plugins from.

```yaml
- id: mcp-mewcp
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: mewcp
    transport: streamable-http
    url: https://gateway.mewcp.com/personal/mcp
    headers:
      Authorization: "Bearer API_KEY"
```

One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry.

1. Open cordis.yml (or your patch file) in your DSH project
2. Paste the entry into your plugin list, keeping the leading dash and indentation
3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__<tool_name>
4. Verify with: dsh web --dump-config | grep -A3 mcp

## SDKs

### Python

fastmcp client

```python
import asyncio
from fastmcp import Client
from fastmcp.client.transports import StreamableHttpTransport

SERVER_URL = "https://gateway.mewcp.com/personal/mcp"
API_KEY = "API_KEY"

transport = StreamableHttpTransport(
    url=SERVER_URL,
    headers={
        "Authorization": f"Bearer {API_KEY}",
    }
)

async def main():
    client = Client(transport)
    async with client:
        tools = await client.list_tools()
        print(tools)

asyncio.run(main())
```

1. Install fastmcp: pip install fastmcp
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run your script

### TypeScript

MCP SDK

```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const SERVER_URL = "https://gateway.mewcp.com/personal/mcp";
const API_KEY = "API_KEY";

const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), {
  requestInit: {
    headers: {
      Authorization: `Bearer ${API_KEY}`,
    },
  },
});

const client = new Client({ name: "mewcp-client", version: "1.0.0" });
await client.connect(transport);

const tools = await client.listTools();
console.log(tools.tools.map((t) => t.name));
```

1. Install: npm install @modelcontextprotocol/sdk
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)