Claude Aurora connectorWhat Claude can do in your Aurora account.
The Claude Aurora connector exposes 4 tools, all 4 of them for reading. 0 write anything, 0 are undocumented. Below: how Claude finds a Consilio matter, opens its workspaces, questions the documents inside, and what Consilio deliberately keeps out of reach.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can open your Consilio matters
With Aurora, you ask Claude your question in plain English instead of digging through the Consilio portal yourself. It locates the matter, picks the right workspace and comes back with an answer that cites the documents it relied on. Every answer stays inside what you are already entitled to see in Consilio's web products.
Pin down the right engagement. Type a client name or the matter's alpha-code and searchMatters returns the matching matters, active ones by default, closed ones if you ask.
See where the review actually lives. A matter often holds several workspaces, say a privileged review and a production set. searchWorkspaces lists them so you know which one to question.
Ask the documents a real question. searchDocuments hands your question to AI Investigate, Consilio's investigation engine, which digs through a workspace and answers with citations: document title, identifier and a matching snippet.
Now the limits. Consilio built Aurora with no write path: nothing gets created, updated, deleted, exported or shared from the chat. Claude sees exactly what your Consilio login already sees. A fourth tool, searchTickets, is read-only like the others, but no source explains what it searches or returns. And nothing runs on its own: no tool fires when a production lands or a deadline nears. Event-driven flows belong to automation platforms, a different job covered from the Integrations hub.
Five words to know first
The vocabulary Claude uses around Aurora, in one minute.
- Connector
- The link you set up once between Claude and an account you already hold, so Claude can work in that account while it answers you.
- Tool
- One named action a connector gives Claude. Claude decides by itself which tools to call, and the directory lists each one by name.
- Authorization
- The service's own sign-in and consent screen, where you hand Claude the access it will use. Granted per person and revocable.
- Approval
- The confirmation Claude waits for before doing something that changes an account, shown inside the conversation when it matters.
- MCP
- The common standard connectors run on: it is what lets an assistant such as Claude talk to an outside service like Consilio.
Connect Aurora to Claude in three steps
- 01
Find Aurora in your settings
Open Claude's settings, go to Customize, then Connectors, and search for Aurora. On a Team or Enterprise workspace, an Owner or Primary Owner must enable it before members can each sign in.
- 02
Sign in on Consilio's side
Click Connect on Aurora's row. Consilio opens its own sign-in window, where your usual single sign-on and multi-factor check apply. If the link breaks later, use Disconnect and connect again.
- 03
Review the consent screen
Before accepting, read the scopes Consilio lists: read-only access to matters, workspaces, documents and tickets. That screen belongs to Consilio, not to Claude, and it is what defines the access you grant.
The 4 tools, all on the reading side
Aurora gives Claude 4 tools: 4 that read your account, 0 that change something in it.
Every tool here looks and reports back. Tool names stay exactly as the directory shows them.
- 4 read
What Claude reads (4)
4 toolsFour tools that query Consilio and leave your matters untouched.
searchMatters
Finds engagements you are entitled to see, from a client name, a short description or an alpha-code (one letter, then five or six digits).
searchWorkspaces
Lists every workspace inside one matter, identified by its alpha-code. You see how the matter is split up before anyone questions the documents.
searchDocuments
Puts a plain-language question to AI Investigate inside a matter's workspace. The engine refines its own searches, then answers with citations pointing to specific documents and passages.
searchTickets
Consilio classes this tool with the rest: read-only. Beyond that, no source says which tickets it covers or what it returns, and the consent screen only names tickets among the scopes.
What Claude asks before it acts
By default, Claude stops and asks for confirmation before each action it carries out on an account for someone, right in the conversation.
On Team and Enterprise, workspace owners decide whether a member may let some actions pass without being asked each time. They can also cap what a connector may do for the whole organization, keeping reads on and writes off, and nobody lifts that from a personal account. With Aurora the question is narrower: Consilio says every request runs as the signed-in user, so Claude reaches what your portal login reaches and nothing else.
Is it on your plan?
Not one of the 819 sheets in the official directory states plan availability. That information is published nowhere, connector by connector.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector before members connect. Consilio's guide states something narrower, quoted in the limits below. For the live state, open Aurora's sheet in the official directory.
Where Aurora stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a document arrives or a matter changes status.
By default the sheet exposes only reading, which is an observed floor rather than a promise: an administrator could open actions no public sheet shows. The partner badge in the directory is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor guarantees their behavior. The same rules apply across the directory, for instance on the Claude activecampaign connector page. Note too that only Consilio documents this connector; no Claude help page covers it.
Which Claude plans can use Aurora?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner enables each one first.
- Consilio's Aurora guide for claude.ai ↗Undated, read October 2026The publisher says custom remote connectors work on Pro, Team and Enterprise, and that the free plan does not expose connectors.
What this page followsThey do not describe the same thing: Anthropic's rule covers every directory connector, while Consilio's undated guide describes adding Aurora as a custom connector. Neither settles it for your account, so check Aurora's directory sheet while signed in.
Need help connecting Aurora to Claude?
A person reads every message.