Skip to main content
Solved

MCP server returns inconsistent / partial tool set — diagram-creation tools never load

  • June 7, 2026
  • 2 replies
  • 91 views

Forum|alt.badge.img+2

I am connecting the Lucid MCP server to Claude (web) on an Individual Lucid plan. The connection authorises fine and basic tools work, but the diagram-creation tools never load.

What I see: across several reconnects in one day, the connector exposes a different partial set of tools each time. Examples of what loads: document search, create folder, create share link, list thread comments, and (in one session) the add/edit/delete shape tools. What never loads in any session: the “create-diagram-from-specification” tool and the “convert-to-diagram” tool.

The odd part: diagram creation worked fine yesterday. I built two diagrams successfully. Today the diagram tools are gone, and disconnect/reconnect does not bring them back.

Already tried:

  • Disconnect and reconnect (three times). Each time a different partial tool set appears; the diagram builders never do.
  • Confirmed this is an Individual plan, so no admin MCP toggle or org-level scope gate applies.

Questions:

  1. Were diagram-creation use cases re-scoped server-side recently? The MCP docs note that new use cases may require re-authentication, and that setup involves a separate permission-scope approval step.
  2. Is a full remove-and-re-add (rather than reconnect) needed to re-grant the diagram scope, or is this a known issue with the server advertising tools inconsistently per session?
  3. Is there a way to confirm which permission scopes my current connection holds?

Any guidance appreciated. Happy to provide timestamps or session detail.

Best answer by renier

Resolved. Posting the answer in case it helps anyone hitting the same symptom.

This turned out not to be a Lucid problem at all. The diagram-creation tools were never missing or re-scoped. They were always available and callable.

The cause was a misunderstanding on the client side about how tools surface. In Claude, the Lucid tools split into two groups. Most load on demand through a tool search, but the diagram builders (create-diagram-from-specification, convert-to-diagram, mind map, org chart, sequence diagram) sit in a directly callable set that the tool search does not index. So every time I checked availability by searching, those tools did not appear, which looked like they had been removed or gated behind a scope. They had not.

What confirmed it: instead of searching for the tool, I just called it directly with a small test diagram. It built first time against the same Individual plan, no re-auth, no scope change. The timing was a coincidence. The tools dropping out of my searches lined up with a plan change, which made an entitlement issue look likely, but the two were unrelated.

So, to answer my own three questions for anyone who finds this later:

  1. No server-side re-scoping. Confirmed with Lucid support.
  2. No remove-and-re-add needed. Reconnecting does nothing because nothing was broken.
  3. The partial tool list from a search is not a reliable picture of what your connection can do. The fix is to call the diagram tool directly rather than judging availability by what a tool search returns.

Thanks to Lucid support for the steerage. Marking this closed.

 

Comments

Forum|alt.badge.img+2
  • Author
  • Answer
  • June 9, 2026

Resolved. Posting the answer in case it helps anyone hitting the same symptom.

This turned out not to be a Lucid problem at all. The diagram-creation tools were never missing or re-scoped. They were always available and callable.

The cause was a misunderstanding on the client side about how tools surface. In Claude, the Lucid tools split into two groups. Most load on demand through a tool search, but the diagram builders (create-diagram-from-specification, convert-to-diagram, mind map, org chart, sequence diagram) sit in a directly callable set that the tool search does not index. So every time I checked availability by searching, those tools did not appear, which looked like they had been removed or gated behind a scope. They had not.

What confirmed it: instead of searching for the tool, I just called it directly with a small test diagram. It built first time against the same Individual plan, no re-auth, no scope change. The timing was a coincidence. The tools dropping out of my searches lined up with a plan change, which made an entitlement issue look likely, but the two were unrelated.

So, to answer my own three questions for anyone who finds this later:

  1. No server-side re-scoping. Confirmed with Lucid support.
  2. No remove-and-re-add needed. Reconnecting does nothing because nothing was broken.
  3. The partial tool list from a search is not a reliable picture of what your connection can do. The fix is to call the diagram tool directly rather than judging availability by what a tool search returns.

Thanks to Lucid support for the steerage. Marking this closed.

 


Ambar D
Forum|alt.badge.img+12
  • Lucid community team
  • June 10, 2026

Hi ​@renier, I’m happy to hear that this has been resolved for you! Thank you for providing such a detailed response in this thread for others who may come across this post.

In an effort to make this thread as helpful as possible to users down the road, I’m adding in a few more details from our development team! 

  • The Lucid MCP server does not require any entitlements and is fully usable by both free and paid users. 
  • The requested permission scopes for the diagram tools have not changed, and re-authorizing should not be necessary. 

Here are a few additional troubleshooting steps we recommend for users who run into this issue in the future:

  • Trying a different MCP client to see if the issue is confined to Claude (MCP inspector would be a good choice, for example).
    • If a different MCP client resolves the issue and it seems to be confined to Claude, we recommend reaching out to Claude for their support.
    • If you can reproduce the issue using a different MCP client, please let us know! There may be additional items for our teams to troubleshoot.

Please let me know if you have any other questions or concerns!