Lucid

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.

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.

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.

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.

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.

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.

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.

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.