Skip to content

FAQ

No. Authentication happens in a browser window against ConsilioId, not inside the client. Your AI assistant only ever receives an OAuth access token scoped to the MCP audience.

No. Every tool Aurora MCP exposes is read-only. There is no write path by design.

What happens if my Consilio access changes?

Section titled “What happens if my Consilio access changes?”

Aurora MCP runs every request as you. If your portal access is revoked, your MCP access disappears at the same instant — no separate off-boarding step is required.

No. It’s a Remote MCP server that calls live Consilio APIs. If the upstream is down, the tools return an error; they don’t serve cached data.

How is this different from a “Claude plug-in”?

Section titled “How is this different from a “Claude plug-in”?”

Aurora MCP implements the Model Context Protocol — an open protocol for tool-bearing servers. While it works perfectly with Claude, it also works with GitHub Copilot, Cursor, and any other MCP-speaking client. There’s no product-specific “plugin” lock-in.

Aurora MCP is operated by Consilio. For isolated-tenant or on-prem arrangements, contact your Consilio account team.

Email support@consilio.com with the word “MCP” in the subject. Include the timestamp, the MCP client you were using, and (if you have it) the request-id from the error.