Lucid
by Lucid
Search Lucidchart and Lucidspark documents, generate diagrams from a prompt, and share them with named collaborators or a link. OAuth sign-in with no scopes to decline, plus a read-only server variant.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Lucid via MCP
https://mcp.lucid.app/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Lucid Tools & Capabilities (11)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Frequently asked questions
Can the Lucid MCP server share my documents with other people?
Yes, and that is the sharpest thing it does. Lucid's help centre documents two sharing actions driven by natural language: creating a shareable link for a document, and adding a named person by email address at a chosen permission level. Lucid's own worked example adds a collaborator with full edit permissions, so a single prompt can grant someone else write access.
What permission does a Lucid share link created through MCP grant?
Whatever role the request asks for, from a four-level scale. Lucid's REST reference defines share link roles as view, comment, edit and editandshare, where editandshare also lets the recipient control who else gets access. Lucid's own MCP example asks for view-only, but view-only is the example rather than a cap the server enforces.
Can a Lucid share link be opened by anyone, including people outside my account?
It depends on your plan, and the default is permissive. Lucid documents link security fields for expiry, passcode, account restriction and anonymous guests, but states these are configurable only on accounts with an enterprise license. Accounts without one get the defaults: no expiry, no passcode, unrestricted access and no anonymous guests.
Which OAuth scopes does the Lucid MCP server ask me to approve?
None that describe what it can do. We read Lucid's own RFC 9728 descriptor on 2026-08-19 and its scopes_supported array is present but empty, while the authorization server advertises only offline_access. Lucid's REST API defines separate sharing scopes, but the MCP server advertises none of them, so there is no read-only option to pick at the consent screen.
Is there a read-only version of the Lucid MCP server?
Yes, two of them, and they are separate endpoints rather than a setting. Lucid's help centre names a read-only MCP server giving AI tools search and view-only permissions, and a repositories MCP server at a distinct URL that grants read-only access to approved Process Accelerator documents. Choosing one at setup is how you decline the write and share surface.
Can my admin stop people connecting Lucid to Claude?
Yes, on Team and Enterprise Lucid accounts. Lucid documents an admin toggle under Admin, Security, AI controls, MCP access that enables or disables MCP for the whole account. Connecting through Claude Team or Enterprise adds a second gate: a Claude organization owner must authorize the Lucid connector before anyone in that organization can link their own account.
Which Lucid plan do I need to use the MCP server?
All of them, per Lucid's own help centre. Lucid lists plan availability for the MCP server as Free, Individual, Team and Enterprise, with one stated exclusion: it is not available on FedRAMP accounts. The repositories MCP server is the exception, requiring the Process Accelerator add-on, which Lucid sells for Enterprise accounts and for the FedRAMP environment.
Does the Lucid MCP server work without a person approving the connection?
Yes, through an API key instead of OAuth. Lucid documents API key authentication for autonomous processes that run with nobody available to grant approval, and states the client then authenticates using that key's permissions with no login or approval prompt at runtime. That removes the consent step, so the key's grants become the only boundary.
Sources
- Lucid help centre, "Integrate Lucid with AI tools using the Lucid MCP server" (fetched 2026-08-19; page states last updated 2026-08-17; resolved 200 with no redirect) · retrieved 2026-08-19
- Lucid help centre, "Connect Lucid to Claude" (fetched 2026-08-19; the live page is titled "Connect Lucid to Claude", without the "and Claude Code" in the directory's slug) · retrieved 2026-08-19
- Lucid help centre, "Integrate AI tools with the Lucid repositories MCP server" (fetched 2026-08-19) · retrieved 2026-08-19
- Lucid developer docs, "Access Scopes" (fetched 2026-08-19) · retrieved 2026-08-19
- Lucid developer docs, "Share Link Security" (fetched 2026-08-19) · retrieved 2026-08-19
- Lucid developer docs, "Create Document Share Link" (fetched 2026-08-19) · retrieved 2026-08-19
- Lucid developer docs, "Generate Embed Session Token" (fetched 2026-08-19) · retrieved 2026-08-19
- Lucid developer docs machine index (fetched 2026-08-19) · retrieved 2026-08-19
- Live auth probe of
https://mcp.lucid.app/mcpand its RFC 9728 / RFC 8414 descriptors — Agentman, 2026-08-19 · retrieved 2026-08-19 - Anthropic connector directory (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Lucid
- Tools
- 11
- Domain
- mcp.lucid.app
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.