Aurora

Search Consilio eDiscovery matters, workspaces and documents from an AI agent.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Aurora connector does

The Aurora MCP server connects Consilio — a global eDiscovery and legal services firm — to Claude, ChatGPT and any MCP-compatible agent. Four read-only tools find matters, list the workspaces inside them, investigate documents and check support tickets. Sign-in is OAuth 2.1 through Consilio Identity, and every request runs as the signed-in user.

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.

Aurora tools (4)

  • searchMatters
  • searchWorkspaces
  • searchDocuments
  • searchTickets

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Consilio mandates human review of anything you rely on. Its terms require independent expert verification by a qualified legal professional of all AI outputs before any output is relied on in a legal proceeding, regulatory filing, court submission, privilege log or legal advice. The same section acknowledges outputs may be inaccurate, incomplete or fabricated, "including references to case law, statutes, or factual matters that do not exist".
  • Privilege risk sits with you. Consilio states the user is solely responsible for assessing and managing privilege risk, and warrants nothing about whether your AI provider's agreement protects it.
  • The tools reference omits one of the four tools. searchTickets is documented nowhere except two mentions in the quickstart, so its arguments and response shape are unpublished.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter detail here comes from the server itself — all of it comes from Consilio's documentation.
  • Scopes do not separate matters from documents in practice. Three read scopes exist, but a consent screen offering documents:read grants the AI Investigate path over evidence text; there is no narrower grant for matter metadata alone.
  • Consilio Identity advertises capabilities wider than this connector uses. Its metadata lists scopes including documents:native, search:read, chat:read, mcp:access and offline_access, and supports the password and implicit grant types alongside authorization_code. Those are properties of the shared identity service, not evidence the connector requests them — but a security reviewer reading the metadata will see them.
  • The advertised PKCE guarantee is weaker in the metadata than in the prose. Consilio's docs say PKCE with S256 is enforced at the gateway. The authorization server's own metadata advertises code_challenge_methods_supported of both plain and S256. We could not test which the gateway accepts.
  • The server's own metadata points at a dead documentation page. The RFC 9728 descriptor declares resource_documentation of https://mcp-docs.ai.consilio.com/aurora-mcp, which rendered Consilio's 404 page on 2026-08-22. The working documentation is the /docs/ tree linked below.
  • The support repository is private. Consilio's FAQ directs feature requests to a GitHub aurora-mcp repository under the consilio-rnd organisation; both URLs returned a Consilio SSO sign-in page rather than a public repository or a 404. Use the support email instead.
  • No numeric rate limit is published. Consilio documents HTTP 429 at a per-tenant cap but states no figure, so throughput is unpredictable until your account team confirms it.
  • It is read-only and online-only. No tool writes anything, and Consilio states the connector serves no cached data — if the upstream Consilio API is down, tools return errors.
  • Availability is gated commercially. Consilio describes Aurora MCP as rolling out to customers and directs new users to an account representative, so the endpoint alone is not enough to get access.

Frequently asked questions

Who actually operates the Aurora MCP server?

Consilio, LLC, a global eDiscovery and legal services firm. Aurora is not a separate vendor — it is the brand name of Consilio's Legal AI Suite, which includes AI Investigate, the engine behind the document tool. Consilio's site reports 5,400 employees and 30,000 hosted matters, so the listing name and the domain describe one company.

Can the Aurora connector change or delete anything in Consilio?

No. All four tools read. Consilio states there is no write path by design, and no tool creates, updates, deletes, exports or shares anything upstream. Anthropic's directory records the permission as Read. The three OAuth scopes the server advertises all end in read, so no grant on the consent screen carries a write.

What OAuth scopes does the Aurora MCP server request?

Three, all read-only: matters:read, documents:read and tickets:read, declared in the server's RFC 9728 resource descriptor on 2026-08-22. Consilio Identity advertises nine more the resource does not request, including documents:native and chat:read. The boundary is real but coarse — no scope separates matter names from document text.

Does using Aurora MCP put attorney-client privilege at risk?

Consilio says it may. Its terms state that transmitting privileged material to a third-party AI environment may give rise to a risk of waiver of legal professional privilege, that preservation depends on your agreement with the AI provider, and that the user is solely responsible for assessing that risk. Consilio disclaims any warranty on the point.

Can I use Aurora MCP with a personal Claude account?

No. Consilio's terms require the connector be used only with credentials tied to an enterprise agreement, and explicitly exclude personal, free-tier, trial and consumer accounts. That agreement must also bar model training on matter data and provide zero or near-zero retention. The FAQ's looser wording about portal accounts does not override this.

What data can the Aurora connector read?

Litigation material about real people. Consilio's privacy notice says a query retrieves document text, custodian details, metadata and review annotations and transmits them to your AI provider. Everything is scoped to your existing portal permissions, so the connector cannot widen access — but within that scope the document tool reaches evidence text directly.

How many tools does the Aurora MCP server have?

Four, per Anthropic's directory: searchMatters, searchWorkspaces, searchDocuments and searchTickets. Consilio's own tools reference documents only three, omitting the tickets tool, which appears elsewhere in its quickstart. Consilio also names its tools with an aurora_ prefix, so neither list matches the other exactly.

Are Aurora MCP tool calls rate-limited or billed separately?

Rate-limited yes, separately billed no. Consilio states no additional licence is needed and usage falls under your existing engagement. Tool calls are subject to per-tenant policy at Consilio's API gateway, which returns HTTP 429 once an organisational cap is reached. Consilio publishes no numeric limit, so ask your account team.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Aurora to work.

Connect Aurora once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.