Connect OneLens to your AI assistant
Ask your OneLens cloud-cost data questions in plain English — directly inside Claude, Cursor, or any MCP-compatible AI host. One URL, one login.
Server URL: https://mcp.onelens.cloud/mcp
Before you start
- An active OneLens account with the MCP feature enabled for your org.
- You'll log in with your normal OneLens credentials.
- Read-only: the assistant can query cost data — it cannot change anything.
Claude Desktop
- Settings → Connectors → Add custom connector
- Name:
OneLens· URL:https://mcp.onelens.cloud/mcp - Click Connect — a browser opens the OneLens login.
- Sign in and Authorize (requests OpenID/Profile/Email + Read Costs).
- Done — “OneLens” shows as connected with its tools.
No custom-connector option on your plan? Edit claude_desktop_config.json:
{
"mcpServers": {
"onelens": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.onelens.cloud/mcp"]
}
}
}
Restart Claude Desktop → the login opens in your browser → tools appear.
Claude (web — Team/Enterprise/Pro)
Settings → Connectors → Add custom connector → paste https://mcp.onelens.cloud/mcp → Connect → sign in → Authorize.
Cursor
Settings → MCP → Add new MCP server → choose HTTP/SSE → URL https://mcp.onelens.cloud/mcp → complete the browser login when prompted.
Try it
Once connected, just ask:
- “List my cost sources.”
- “Top 5 AWS services by spend last month.”
- “Month-to-date spend vs the previous month.”
- “Break down EC2 cost by region for the last 30 days.”
- “Show squad-wise cost last month.”
The assistant discovers your available clouds, dimensions, and values automatically — you don't need to know field names.
Good to know
- Login frequency: sign in once; your session lasts ~14 days and refreshes silently. No hourly re-login.
- Privacy: a stateless proxy — stores no cost data, never logs cost values, scoped to your org. See Privacy.
- Access control: your OneLens admin manages who can use MCP; access can be revoked instantly.
Troubleshooting
| Symptom | Fix |
|---|---|
| Login page errors on connect | Confirm you're using https://mcp.onelens.cloud/mcp exactly; retry. |
| “access denied / not licensed” after login | Your org/user isn't entitled for MCP — contact your OneLens admin. |
| Tools list is empty | Disconnect, clear the connector, reconnect to re-run login. |
| Connected but no data | Make sure your org has cost sources configured in OneLens. |
Still stuck? Contact OneLens support with the time of the attempt — every request has a trace id we can look up.