OneLens
OneLens connects your cloud-cost and FinOps data to Claude. Ask about spend in plain English and get real answers from your live OneLens analytics — no dashboards, no field names to memorize. Query across AWS, GCP, Azure, OCI and cross-cloud allocation views: list your cost sources and dimensions, break spend down by service, account, region, tag, or cost center, see top-N drivers, month-over-month deltas, and daily trends, and drill from account → service → region → SKU. Read-only and secure: you sign in with your OneLens account via OAuth; every query is scoped to your organization and honored by your existing entitlements. The connector stores no cost data and never logs cost values. Your OneLens admin controls who can use it and can revoke access instantly. Requires an active OneLens account with the MCP feature enabled.
View in the Claude registry- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Primary Subcategory
- Cloud Cost Management (FinOps)
- Secondary Subcategories
- None listed
- Brand
- OneLens
- Access
- Account required
- First tracked
- 2026-07-01
- Tool count
- 5
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is visible.
Claude Discoverability Score
Live · refreshed daily. Last refreshedOneLens in Cloud Cost Management (FinOps)
#9of 10competitors
This is the score for the Integration’s Primary Category, Cloud Cost Management (FinOps). OneLens's tools align with this Category, which is why we measure it here. Claude did not find it in connector search, show it in the connector picker, or invoke it in the measured contested Runs. That is why the score is 0.
How this score is measuredWhat we measure
One core score. Three important factors to discoverability.
- Sets the score
Picked
· 0/100 - Diagnostic
Found
· 0/100 - Diagnostic
Positioned
· 0/100
Competing in Claude Cloud Cost Management (FinOps)
View CategoryWhat does 0/100 mean?
0 is OneLens's rounded picker appearance rate. It appeared in the connector picker, or Claude invoked it directly, in 0% of contested conversations. All three measures are important to discoverability: Picked determines the headline score, Found shows how often Claude found OneLens in connector search, and Positioned shows where it appeared in the picker.
OneLens is 10 points from Buried.
FoundDiagnostic
Whether Claude found your Connector in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.
PickedMain score
How often your Connector appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.
PositionedDiagnostic
What position your Connector appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.
5 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are OneLens alternatives on Claude?
As of 2026-08-14, OneLens competes with ClickHouse, Phoenix by HG Insights, AWS MCP, Harness, Datadog, Snowflake, Cloud Cost Coach, Costory, Wiv in Claude Cloud Cost Management (FinOps), ranked by public Discoverability Score.
Where does OneLens rank in Cloud Cost Management (FinOps) on Claude?
As of 2026-08-14, OneLens ranks #9 of 10 in Claude Cloud Cost Management (FinOps) with a Discoverability Score of 0/100 (Invisible).
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.