Connect Lucidity to Your AI Assistant (MCP Server)

The Lucidity MCP server lets your team ask about savings, storage and onboarding from inside the AI assistant you already use, without opening the Lucidity dashboard.

Jump to your assistant: Claude Code | Claude web and desktop | OpenAI Platform

Connection URL

There are two Lucidity environments. Use the one that matches the dashboard you sign in to.

If your dashboard is	Your connection URL is
`https://www.web.lucidity.dev`	`https://lucid-mcp.prod.lucidity.dev/mcp`
`https://web-azurepls.lucidity.cloud`	`https://lucid-mcp-azurepls.lucidity.cloud/mcp`

No trailing slash. Adding one makes some clients fail with a Lucidity error page during sign-in. Copy the URL exactly as above.

Two ways to connect

Which one you use depends on your llm client.

Type	How it signs in	LLM Client
Interactive	You sign in through your browser when you connect. Nothing to configure.	Claude Code, Claude web, Claude desktop
Token	We issue you an access token, which you paste in. There is no browser sign-in because there is no browser.	OpenAI Platform, and anything you build with an API or agent framework

Before you start

A Lucidity account you can sign in to. Your existing single sign-on works for the interactive assistants.
For the token type, ask us for an access token and tell us which Lucidity account it should cover.
You see exactly the accounts and data your Lucidity role already gives you. Connecting cannot widen your access.
All write actions are disabled, so the connection is read-only in effect.

Claude Code

Add the server, then authorize it.

claude mcp add --transport http lucidity https://lucid-mcp.prod.lucidity.dev/mcp

Run /mcp and choose lucidity. A browser opens, you sign in, and an Authorize App screen appears. Choose Accept. The terminal confirms the connection.

Authorization request for app access to Lucidity account with specific permissions listed.

Claude web and desktop

Open Customize in the left sidebar, then Connectors. Connectors used to sit under Settings and have moved.
Choose Your connectors, then Add custom connector.
Name it Lucidity and paste the connection URL above.
Choose Connect. A browser tab opens with the Authorize App screen. Choose Accept.
The connector now shows Connected.

List of connected connectors with 'lucidiy' highlighted in the interface.

The first time Claude uses a Lucidity tool it asks your permission. Choose Always allow so it does not ask again for that tool.

Create an API key

Do this only for the API key type.

Sign in to the Lucidity dashboard.
Open Settings, then API key.
Choose Create key.
Give the key a name, and choose an expiry: no expiry, 30, 90 or 365 days.
Copy the key.

The key is shown once. Copy it before you close the dialog. If you lose it, delete the key and create a new one. Lucidity cannot show it to you again.

The key is one long string, not a pair of values. There is no separate client ID and client secret.

The key acts on your behalf. On each account, it has the same access your own role has. Treat it like a password.

OpenAI Platform

This covers the OpenAI Platform playground and anything you build on the Responses API or an agent framework. These call Lucidity from a server, so there is no browser sign-in. You paste in an API key instead.

Create your key first. See "Create an API key" above.

In the playground, open MCP server under Hosted tools, then Connect to MCP Server.
URL: paste the connection URL above.
Label: Lucidity
Authentication: choose Access token / API key. There is no OAuth option here, which is expected.
Paste your Lucidity API key, then choose Connect.

Form to connect to MCP Server with URL, label, description, and authentication fields.

One account per token. A token is issued against a single Lucidity account, fixed when we create it. You cannot switch accounts inside the session. If you need more than one, ask us for a token per account.

Check it works

Ask: What is our realized savings?

You should get a figure, the period it covers, and the number of cloud accounts behind it. Compare it with the Realized to date tile on your dashboard.

What you can ask

Topic	Examples
Savings	What is our realized savings? What is our projected annual saving? How much more could we save by onboarding?
Storage	What is our storage utilization? How much storage do we manage?
Inventory	How many VMs are managed? Which VMs are unmanaged? Which are shut down? Are any agents down?
Onboarding	How far along is our onboarding? Which onboarding jobs failed and why? Is anything waiting for cleanup?
Policies	List our scaling policies. What thresholds does a policy use? Which policy is on this VM?
One VM	Tell me about this VM. Which mount points does Lucidity manage on it?

What it cannot answer yet

The split between cost reduction and cost prevention.
Storage tiering recommendations.
Unattached or idle disks.
Whether a scaling policy still fits its storage pool.
Questions about how Lucidity works. Use this documentation for those.

Troubleshooting

What you see	What to do
A Lucidity page saying "Oops, something went wrong" during sign-in	The URL has a trailing slash. Remove it and reconnect.
"Unauthorized" after a couple of hours of use	The browser session has expired. Reconnect the server. In Claude Code, run `/mcp`.
"Unauthorized" on a token connection	The token has expired or been revoked. Ask us for a new one.
A permission prompt on every question	Choose Always allow rather than Allow once.
Only one account is visible	Expected on a token connection. Each token covers one Lucidity account.
A figure that does not match your dashboard	Check the period. Realized savings defaults to the last 365 days, and the dashboard tile is all time. Ask for a specific window, or contact Lucidity support.

Other assistants

These are not ready yet. Contact Lucidity support before you attempt them.

Assistant	Status
ChatGPT app, Business or Enterprise	Your workspace administrator must enable Developer mode first. There is no standard connector path. This is separate from the OpenAI Platform section above, which does work.
Gemini Enterprise	Needs a client ID and secret that Lucidity issues per customer, plus two Lucidity domains allowed in your Google Cloud organization policy. Ask us and we will send the values.
Gemini CLI	Connects successfully, but the CLI itself needs a Google Code Assist license.
Copilot Studio, Microsoft Foundry	Not yet assessed. Foundry agents will use the token method above.