Skip to main content
Version: 2026.09

Connect an MCP client

Connect an MCP-compatible AI client to the Istari Digital MCP Service and authenticate through an interactive browser sign-in.

LLM integration and customer responsibility​

Read this notice before connecting an AI service to production data.

By connecting the Istari Digital Platform to your own large language model (LLM) or other AI system, you acknowledge these responsibilities:

  • Data spill risk — Chat history or model-training settings can expose sensitive or proprietary information. You are responsible for configuring the AI service to protect that data.
  • Customer responsibility — You are responsible for the AI service’s privacy settings, security controls, output accuracy, and legal and contractual compliance.
  • Preview use — If you use a beta version before Istari Digital’s internal cyber approval, you accept it as-is and at your own risk.
  • Liability — Istari Digital disclaims liability for loss, damage, or claims arising from your AI integration. Your applicable agreement with Istari Digital governs the complete terms.

Proceed only after you understand and accept these risks and responsibilities.

Before you start​

You need:

  • an MCP-compatible client that supports remote HTTP servers and OIDC;
  • an Istari Digital account with access to the Resources and operations you need;
  • the MCP endpoint for your deployment from your administrator.

The endpoint follows this form:

https://mcp.<your-istari-domain>/mcp/

For example, one development environment uses:

https://mcp.dev2.istari.app/mcp/

Connect and authenticate​

  1. Register your deployment’s endpoint as a remote HTTP MCP server in the client.
  2. Trigger sign-in using that client’s command or settings.
  3. Complete the OIDC sign-in in the browser.
  4. Confirm that the client reports authenticated, not only connected. A reachable endpoint can still be unauthorized.

When the session expires, sign in again. You do not need to re-add the server.

Do not add an Authorization: Bearer header to client configuration, command arguments, chat logs, or commits. Personal Access Tokens are not accepted. If an old configuration contains that header, remove it and reconnect with OIDC.

If your client is not documented here, follow the four generic steps above rather than guessing its configuration format.

Test the connection​

Ask the assistant to find a read-only method before requesting a write:

Find the Istari Digital method for listing Systems, then list the first five Systems I can access.

The client should call search to identify the method and execute to run it. See the API reference.

For a coding agent that can work with local files, see Get started with Claude Code.