Page History

...

Starting with version 3.5.0, iDNA Applications includes an MCP server. MCP (Model Context Protocol) is the open standard through which AI assistants access external data. With the MCP server enabled, AI clients such as Claude, GitHub Copilot or OpenAI Codex can answer questions about your Notes/Domino estate from your live iDNA data: application usage, design and code analysis, modernization and lifecycle planning. The recommended way to use it is the iDNA Applications Companion, an AI-assistant plugin for these clients (see the knowledge base article Setting up the iDNA Applications Companion).

• Read-only: the MCP server reads iDNA's analysis data. It cannot change iDNA, your Domino environment or any configuration.
• Runs on your appliance: the MCP server is an optional service of the iDNA appliance and is disabled by default. Once enabled, it is reachable at https://<your iDNA host>/mcp through the existing HTTPS port; no additional firewall port is needed. AI clients connect from the user's machine, so the appliance does not have to be reachable from the internet.
• Personal tokens: every user authenticates with their own token. Administrators see all tokens and can revoke any of them.
• Two modes, set by your license:
  • Restricted: the AI works with an allowlist of iDNA's data; the detailed user-activity tables are excluded.
  • Permissive: the AI can access all of iDNA's analysis data, including detailed user activity.
  The appliance enforces the mode, regardless of the AI client or model. For details on what each mode includes, contact support@panagenda.com.
• Audit log: the MCP server logs every request together with the token it came from.

...

How to connect the AI clients with the token is described in the knowledge base article Setting up the iDNA Applications Companion.

Managing Tokens Centrally

...