Aura
by Aura
Query Aura Intelligence workforce data — headcount, hiring, attrition, subsidiaries — from an AI agent. Six read-only tools return company-level aggregates; Aura states no personal employee data is returned, though the database behind it holds 1 billion individual profiles.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Aura via MCP
https://mcp.auraintelligence.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Aura Tools & Capabilities (6)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Aura's nominated documentation host is dead.
docs.getaura.aipresents a TLS certificate that expired on 2026-03-02 and, with the certificate bypassed, returns a VercelDEPLOYMENT_NOT_FOUND404 on every path we tried. It is the URL Anthropic's directory publishes and the target of both Install buttons on Aura's MCP page. This page is built from Aura's marketing, FAQ, legal and blog pages instead, all of which are live. - Aura publishes no tool list. The six names come from Anthropic's directory. Aura's own page describes capabilities in prose, so our diff is a semantic label match and a rename would not show up in it.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here — including whether any minimum-cell-size rule protects aggregates over very small populations.
- No scopes exist to narrow the grant. The RFC 9728 descriptor declares
scopes_supportedas an empty array. This matters less than usual because the surface is read-only, but it means consent is all-or-nothing across all six tools. - Redistribution is contractually restricted. Aura's terms limit use to the customer's internal purposes and forbid disclosing or distributing information obtained from the Services without Aura's consent. An agent that drafts an external deliverable from connector output can breach this without anyone noticing.
- The data is estimated, and Aura says so. Aura's FAQ states there is "no 100% accurate method or data source for determining internal company metrics", claims 91% accuracy against 65% for traditional methods, and says it publishes per-company Confidence Rankings. Those rankings are not exposed by any listed tool, so an agent cannot check the reliability of a figure it reports.
- Headcount will disagree with a company's own reporting. This is inherent to outside-in estimation, and Aura states it deliberately does not algorithmically scale its data to compensate. Do not present these numbers as audited figures.
- The connector is beta. Aura's own wording asks users to acknowledge bugs, errors or unexpected results.
- ChatGPT is not supported yet. Aura's MCP page lists ChatGPT as "Coming Soon" and names Claude Desktop as the current integration, despite the connector being usable by any MCP client that can complete its OAuth flow.
- Aura's privacy notice is overdue for review. The published version is v1.0, issued 2025-02-18 in its document control block with a stated next review of June 2025 — a review date more than a year past.
Frequently asked questions
Aura states it does not. Its MCP page says data comes from publicly available information, that no personal employee data is included in any responses, and that data is aggregated and anonymized where applicable. All six tools return company-level counts and breakdowns. The individual-level corpus exists but Aura places it behind this aggregate boundary.
From six source families Aura names in its FAQ: public government records, online professional profiles carrying a person's work history and education, job advertisements, layoff notifications, partner data companies, and employee sentiment reviews. Aura's FAQ states this covers 20 million companies, 1 billion employee profiles and 500 million job postings.
None that narrow anything. The server's RFC 9728 descriptor declares scopes_supported as an empty array, verified live on 2026-08-23, so consent grants access to the whole tool surface rather than a chosen part. Because all six tools are read-only, no boundary is needed between a routine read and an irreversible write.
No. All six tools listed are reads: find, get, analyze and breakdown verbs only. Anthropic's directory records the permission as Read. No tool takes a service, method or action argument that would forward to a wider API, so the read-only classification is not hiding a dispatcher behind an honest-looking name.
Aura's nominated documentation host, docs.getaura.ai, is broken two ways. Its TLS certificate expired on 2026-03-02, and requests that bypass the certificate return a Vercel DEPLOYMENT_NOT_FOUND 404. Both Install buttons on Aura's own MCP page point there, so the documented install path does not work. Use the setup steps below instead.
Not without permission. Aura's Terms of Use restrict the licence to the customer's internal use and forbid copying, disclosing or distributing any information obtained from the Services without Aura's consent. A separate clause bars extraction. Pasting connector output into a client deliverable or public report needs Aura's agreement first.
Yes. The MCP endpoint sits on mcp.auraintelligence.com while the documentation sits on getaura.ai, which looks like a mismatch but is not. Fetching auraintelligence.com on 2026-08-23 returns a 301 redirect to www.getaura.ai. Aura Intelligence, Inc. is a Delaware corporation that spun out of Bain and Company in 2024.
An existing Aura account and a Claude Desktop Enterprise subscription, which Aura's MCP page names as a requirement. Aura labels the connector a beta tool and asks users to acknowledge they may encounter bugs, errors or unexpected results. Non-customers are directed to contact Aura's sales team rather than self-serving access.
Sources
- Aura MCP server page (retrieved 2026-08-23). Carries the capability bullets, the privacy and compliance statement, and the beta acknowledgement. · retrieved 2026-08-23
- Aura FAQ, data sourcing and coverage (retrieved 2026-08-23) · retrieved 2026-08-23
- Aura Terms of Use (retrieved 2026-08-23) · retrieved 2026-08-23
- Aura External Privacy Notice v1.0 (retrieved 2026-08-23) · retrieved 2026-08-23
- Aura product overview (retrieved 2026-08-23) · retrieved 2026-08-23
- Aura blog, "How Aura Intelligence Leverages Anthropic's Claude AI" (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: anonymous initialize to
https://mcp.auraintelligence.com/mcpreturned 401 with aWWW-Authenticate: Bearerchallenge; RFC 9728 metadata athttps://mcp.auraintelligence.com/.well-known/oauth-protected-resource/mcp; authorization server metadata athttps://mcp.auraintelligence.com/.well-known/oauth-authorization-server(2026-08-23) · retrieved 2026-08-23 - Dead documentation host check:
https://docs.getaura.ai/— expired TLS certificate (notAfter 2026-03-02), VercelDEPLOYMENT_NOT_FOUND404 with certificate verification disabled (2026-08-23) · retrieved 2026-03-02 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Aura support — <mailto:support@auraintel.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Data & Research
- Developer
- Aura
- Tools
- 6
- Domain
- mcp.auraintelligence.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.