Someone on your team wants to connect Lucidity to your company's AI assistant. Your assistant lets only an administrator add a new connector. This page gives you what you need to review and approve it.
Setup takes about five minutes. After you add the connector once, each user connects with their own Lucidity login.
What the connector does
The Lucidity MCP server lets users ask questions about their Lucidity data from inside the AI assistant. For example:
- How much have we saved this month?
- Which VMs are pending onboarding?
- Did last night's onboarding job finish?
It answers from live Lucidity data: savings, storage use, VM inventory, onboarding jobs and scaling policies.
Security at a glance
| Question | Answer |
|---|---|
| Can it change anything? | No. All write actions are disabled. The connector is read-only. |
| What can a user see? | Only the accounts and data their Lucidity role already gives them. Connecting cannot widen their access. |
| Is there a shared service account? | No. Each user signs in as themselves. |
| How do users sign in? | OAuth 2.0 in the browser, with their normal Lucidity login and single sign-on. |
| Do you need a client ID and secret from us? | No. The server supports dynamic client registration, so the assistant registers itself. |
| Does it read disk contents? | No. It reads the same metadata the Lucidity dashboard shows. |
| Can users reach it without your approval? | Only if your assistant lets users add their own connectors. |
| Can you remove it? | Yes. Remove the connector in your admin settings, and access stops for everyone. |
Details you need
Use the environment that matches the dashboard your users sign in to.
| If your users sign in at | Connection URL | Sign-in domain |
|---|---|---|
https://www.web.lucidity.dev |
https://lucid-mcp.prod.lucidity.dev/mcp |
auth.lucidity.dev |
https://web-azurepls.lucidity.cloud |
https://lucid-mcp-azurepls.lucidity.cloud/mcp |
auth-pls.lucidity.cloud |
Do not add a slash at the end of the URL. With a trailing slash, sign-in fails on most assistants.
If your network or policy limits outbound domains, allow both the connection URL domain and the sign-in domain.
Claude Team and Enterprise
You must be an Owner or Primary Owner.
- Open Organization settings, then Connectors.
- Choose Add custom connector.
- Name it
Lucidity, and paste the connection URL. - Leave the OAuth client ID and secret empty.
- Choose Add.
Your users can now open the + menu in a chat, choose Connectors, and connect Lucidity. Each user signs in once with their Lucidity login.
Microsoft Copilot Studio
Lucidity has not yet tested Copilot Studio. The steps below follow Microsoft's documentation. Contact us before you start, and we will join the setup.
You need a Copilot Studio licence, the Environment Maker role (or higher), and a data policy that allows MCP servers.
- Open your agent, then Tools.
- Choose Add a tool, then Model Context Protocol.
- Enter the name
Lucidity, a short description, and the connection URL. - For authentication, choose OAuth 2.0, then Dynamic discovery.
- Save, then sign in with a Lucidity login to test.
Other assistants
| Assistant | What to do |
|---|---|
| ChatGPT Business or Enterprise | A workspace admin must turn on Developer mode first. Contact us before you start. |
| Gemini Enterprise | Needs a client ID and secret that we issue for your organization. Contact us and we will send them. |
| OpenAI Platform, or an agent you build | No admin step. The user creates an API key in Lucidity and pastes it in. See the user guide. |
After you approve
Send your users the user guide: Connect Lucidity to Your AI Assistant. It shows them how to connect and what to ask first.
Questions
Contact Lucidity support or your Lucidity contact. We are happy to join a short call while you set it up.