Subject: Lucid MCP connector tools declared and connected, but never reach the tool list in Claude Code sessions

SUMMARY

The Lucid connector for Claude (mcp.lucid.app/mcp) is connected and shows "Connected" status, with 7 tools listed on its own directory page (claude.ai/directory/lucid). None of these tools have ever become callable in any Claude Code session tested - not the session that originally connected it, and not a brand-new session opened specifically to test whether a fresh session would pick them up.

ENVIRONMENT

• Product: Claude Code (not claude.ai's own web chat)
• Connector: Lucid, connector URL https://mcp.lucid.app/mcp
• Connector status: "Connected" (confirmed via claude.ai/directory/lucid, sign-in requirement satisfied)
• Connector registration level: organization-wide, not per-user custom - confirmed by attempting to add it again via "Add custom connector" with the same URL, which was rejected: "A connector with this URL already exists in your organization. Use the existing connector instead of adding it again."

WHAT THE CONNECTOR PAGE SHOWS (claude.ai/directory/lucid)

Tools (7): lucid_create_embed, lucid_create_embed[truncated], fetch, lucid_create_docume[nt], lucid_create_mind_map, lucid_create_org_chart, lucid_create_diagram[truncated], lucid_create_sequenc[e diagram], search, share_document_with[...], lucid_export_docume[nt]

Prompts (2, separate MCP capability, not part of this issue): ui://lucid-image-viewer/lucid-image-viewer.html, ui://lucid-viewer/lucid-viewer.html

STEPS TAKEN TO DIAGNOSE

1. In the original Claude Code session, searched for the connector's tools via keyword ("lucid", "lucid diagram create", etc.) - no results.
2. Searched for the exact tool names shown on the connector page (lucid_create_diagram, lucid_create_org_chart, lucid_create_sequenc, lucid_create_mind_map, search, fetch, share_document_with, lucid_export_docume, lucid_create_docume, _lucid_create_embed) - no results.
3. Opened a brand-new Claude Code session specifically to test whether a fresh session would pick up the connector (a different, unrelated first-party connector - Atlassian/Confluence - had its tools pushed into the running session live, mid-conversation, immediately upon connecting, so this was a reasonable first theory). Result: the new session also could not find any Lucid tools by the same searches. This rules out a stale-session/needs-restart explanation.
4. Attempted a direct HTTP request to the connector URL (https://mcp.lucid.app/mcp) to sanity-check the endpoint is live. Got HTTP 405 Method Not Allowed, which is expected/uninformative for an MCP server (it only responds to proper JSON-RPC POST requests, not a plain GET) - confirms the endpoint exists and is reachable, but doesn't reveal anything about why tools aren't surfacing.
5. Attempted to re-add the connector via "Add custom connector" using its known URL, to see if that would help - blocked by Claude's own duplicate-connector check (see above), confirming the registration is real and singular, not something broken on the registration side.

WHAT THIS RULES OUT

• Not a stale-session issue - tested and disproven in a fresh session.
• Not a missing/duplicate registration - Claude's own UI confirms exactly one registration exists at the org level.
• Not the connector being down - the endpoint responds (405, not a connection failure or timeout).

WHAT THIS POINTS TO

Some gap specific to how Claude Code (as opposed to claude.ai's own chat surface, which is presumably how this connector is normally used, per the product description "generate foundational Lucidchart diagrams directly from your conversation") retrieves or registers this connector's declared tools. The tools are declared, visible, and the connector shows connected/authenticated - but they never reach the point where Claude Code's own tool-search mechanism can find them.

ASK

1. Is the Lucid MCP connector expected to work with Claude Code specifically, or only with claude.ai's own chat interface? If the latter, that would fully explain this and there's nothing to fix - just a product-scope clarification we need.
2. If it's meant to work with Claude Code too, can you check server-side whether tool-list requests from a Claude Code session are reaching mcp.lucid.app/mcp and what they're returning?