Skip to content

claude.ai

claude.ai supports custom Remote MCP connectors on Pro, Team, and Enterprise plans. The free plan does not expose connectors. Once added, the connector is available in every chat under your account.

  • A claude.ai account on Pro, Team, or Enterprise.
  • A Consilio account that can sign in at auth.ai.consilio.com.
  • A modern browser (the OAuth flow uses a popup window).
  1. Open Settings → Connectors → Add custom connector.
  2. Paste the Aurora MCP endpoint:
    https://mcp.ai.consilio.com
  3. Name it Consilio (or whatever’s memorable for you).
  4. Click Add.

claude.ai fetches https://mcp.ai.consilio.com/.well-known/oauth-protected-resource, discovers Consilio Identity as the authorisation server, and immediately initiates the OAuth handshake. You don’t paste a client ID, secret, or scope list — the protocol handles all of it.

Claude will open a browser tab for auth.ai.consilio.com. Sign in as yourself. SSO and MFA work as they do on the Consilio portal.

You’ll then see a consent screen describing the requested scopes (read-only access to your matters, workspaces, documents, and tickets). Approve it; the tab closes itself and claude.ai lights up the new connector.

Back in claude.ai, start a new chat and try:

Show me my active matters for Coho Capital.

You should see your assistant invoke the searchMatters tool and return your matters. Every answer is scoped to what you can already see in the Consilio portal — nothing more, nothing less.

If you don’t see the Consilio chip in the chat composer, click the Connectors icon in the composer and toggle Consilio on for this chat.

The OAuth tab closed before the handshake finished, or your browser blocked the popup. Re-authorise from Settings → Connectors → Consilio → Reconnect, allowing popups for claude.ai and auth.ai.consilio.com.

You have no matters matching the query. Verify portal access at portal.consilio.com first; Aurora MCP only ever returns matters you can already see there.

Connector appears but tool calls error with 401

Section titled “Connector appears but tool calls error with 401”

Token expired or audience binding rejected the request. Click Reconnect on the connector card to refresh.

Custom connectors are off at the workspace level (Enterprise only). Ask your workspace admin to enable Custom Connectors in workspace settings.

Tool call returns “ElicitationUnsupportedError”

Section titled “Tool call returns “ElicitationUnsupportedError””

Aurora MCP needs to ask you a clarifying question (e.g. “which matter?”) but claude.ai didn’t surface the elicitation prompt. Re-ask with a narrower query — include the matter alpha-code or full client name.

  • Try Claude Desktop on the same account; tool history syncs through your Claude profile.
  • Read the Security model for the full token lifecycle.
  • See the FAQ for support, SLA, and incident contacts.