Page History

...

• 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 at any time.
• 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.

Note: data that the AI retrieves through MCP becomes part of the AI conversation and is processed by the AI model of the client in use your organization uses (for example by Anthropic, GitHub/Microsoft or OpenAI). Whether that is acceptable for your organization is decided Your organization decides before MCP is enabled whether iDNA data may be processed this way, which is why MCP requires a double opt-in (see Step 1).

Configuration

Setup at a glance:

...

• Version: iDNA Applications 3.5.0 or later.
• License: MCP must be enabled in your license. MCP is free of charge; see Step 1 and the section Licensing.
• Network: users' machines reach the iDNA appliance over HTTPS (port 443), the same way they reach the iDNA web interface (through VPN where applicable).
• Access: an iDNA administrator account and SSH access to the appliance (for example via PuTTY).

...

1. Connect to the appliance via SSH.

2. Open the configuration file /opt/panagenda/appdata/ifa/config and set:

   Code Block
   language bash
   PANAGENDA_ENABLE_MCP=true

3. Apply the change by running this command in the SSH session:

   Code Block
   language bash
   ifa recreate

...

On this first start, the appliance generates an admin token for the MCP service and saves it as PANAGENDA_MCP_ADMIN_TOKEN in the same configuration file. iDNA uses it to manage the users' tokens; no further action is needed (see Security Notes).

From now on, the MCP server is available at https://<your iDNA host>/mcp. Users need this address to connect their AI clients.

...

MCP is included in iDNA Applications 3.5.0 and later at no additional cost. It is enabled through a new license that panagenda issues on request, after your organization has confirmed the mode and the internal clearance (see Step 1). Contact support@panagenda.com.