Lucidchart is where teams draw flowcharts, org charts, process maps, and system diagrams that the whole company reads. Connecting Lucidchart to clariBI turns that diagram library into something you can count: how many documents exist, who owns them, when they last changed, and who collaborates on them.
Why connect Lucidchart
A growing Lucidchart workspace becomes hard to audit by hand, so questions about how many process maps exist or which diagrams went stale mean clicking through folders one at a time.
With Lucidchart connected, you can ask "How many documents has each team created this quarter?", "Which diagrams have not been touched in six months?", or "Who are the collaborators on our onboarding flowchart?" and the AI engine reads it live.
How the connection works
clariBI talks to Lucidchart through its hosted MCP server at https://mcp.lucid.app/mcp. Authentication uses an OAuth flow that clariBI registers itself for (no developer console setup on your side). Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Lucidchart
U->>C: Click Authorize with Lucidchart
C->>V: Open OAuth authorization
V-->>U: Grant read access?
U->>V: Approve
V-->>C: Authorization code
C->>V: Exchange code for tokens
V-->>C: Access + refresh tokens
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Lucidchart tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Lucidchart cannot modify data on the vendor side.
The exact tool inventory depends on the Lucidchart features your account has access to. After connecting, try a few natural-language questions to see what Lucidchart data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Lucidchart, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Lucidchart
U->>C: Ask a question about diagram and document inventory data
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Lucidchart card.
- Click Authorize with Lucidchart.
- Sign in to Lucidchart in the popup window and grant the requested read scopes.
- Back in clariBI, give your data source a name.
- Click Finish.
Permissions and data access
clariBI connects through Lucidchart's OAuth flow and inherits the connected user's document access. The catalog exposes read tools only (searching documents, reading document and page metadata, listing collaborators, exporting a page to an image); clariBI never edits a diagram, shares a document, or changes collaborators. Disconnect anytime from Settings → Integrations in clariBI.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "No documents returned" | The connected user owns or can see no documents matching the search, or the documents sit in a folder the account cannot reach. | Confirm the document exists for your user in Lucidchart and try a broader search keyword. |
| "Collaborator list looks short" | Lucidchart returns collaborators in pages, and only the people with an explicit role on the document or its folder appear. | Ask the analysis to page through all collaborators, and remember that view-link viewers are not listed as named collaborators. |