Skip to main content
Version: 2026.08

Quick Start

Welcome to the Istari Digital Model Concept Protocol (MCP) Service. This quickstart guide will help you connect and interact with the server using compatible MCP clients.

Istari Digital Legal Disclaimer – LLM Integration and Customer Responsibility​

IMPORTANT NOTICE – READ CAREFULLY

By connecting Istari's software collaboration platform ("Istari Platform") to your own Large Language Model ("LLM") or other AI system, you acknowledge and agree to the following terms and responsibilities:

  1. DATA SPILL RISK – If chat history is enabled or Istari-connected data is used to train your LLM, sensitive or proprietary information may be exposed. You are solely responsible for preventing and mitigating such risks.

  2. CUSTOMER RESPONSIBILITY – You are solely responsible for your LLM's configuration, privacy settings, security controls, and output accuracy, and for ensuring legal and contractual compliance.

  3. BETA USE (IF APPLICABLE) – If you use a beta version before Istari's internal cyber approval, you accept it "AS IS", without warranties, and entirely at your own risk.

  4. LIABILITY SHIFT – Istari disclaims all liability for any loss, damage, or claim arising from your LLM integration. You agree to indemnify Istari for any such matters.

By proceeding with the LLM integration, you acknowledge that you have read, understood, and accepted this disclaimer, and you assume all risks and liabilities associated with such integration.

Istari Digital MCP Service Endpoint​

You can access the Istari Digital MCP Service remotely at:

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

Authentication (OIDC)​

The MCP service authenticates with OIDC: an interactive browser sign-in. The client stores the credential. Personal Access Tokens are not accepted.

Generic steps (any MCP client)​

  1. Register the endpoint in the client as an HTTP MCP server. Use your installation's URL (https://mcp.<your-istari-domain>/mcp/). The example host below is one environment; ask your admin if you do not know yours.
  2. Trigger sign-in with that client's command or UI. Approve in the browser when it opens.
  3. Confirm the client reports authenticated, not only that the transport connected. A reachable server can still be unauthorized.
  4. When the session lapses, sign in again. Do not re-add the server.

Do not put an Authorization: Bearer header in a config file, a command, a chat log, or a commit. If you already have that header, the setup is stale — remove it and start from step 1.

If this page does not list your client, stop at these four steps rather than guessing that client's config format.

Tools​

The LLM interacts with the Istari platform through two tools:

  • search — discover available Istari API methods and their parameters
  • execute — call the Istari API on behalf of the authenticated user

See the API Reference for details.

Connecting the Istari Digital MCP Service to Common MCP Clients​

Register https://mcp.<your-istari-domain>/mcp/ (or the example https://mcp.dev2.istari.app/mcp/ if that is your environment) as a remote HTTP MCP server, then complete the client's OIDC sign-in in the browser. Do not add a Bearer token to claude_desktop_config.json or to mcp-remote --header arguments.

For Claude Code, see Start with Claude Code.

You're now ready to use the Istari Digital MCP service to automate workflows and integrate digital engineering models with your LLM-powered tools!