MCP Integration
MCP Integration
AtomIQ exposes an MCP server at /api/mcp on the same host and port as the REST API (default http://localhost:8091/api/mcp). Configure an HTTP/SSE MCP client such as Cursor or Claude Desktop to use that URL.
On z/OS, IBM i, or behind a proxy, set OL_MCP_BASE_URL to the URL clients should use.
Start AtomIQ, confirm the endpoint, and run list-workspaces or query-workspace-app-data as a smoke test. Most MCP tools accept an optional workspaceId; when omitted, AtomIQ uses the default workspace.
The MCP endpoint is excluded from browser host-auth gating. Protect its network exposure in production. Configure workspace integrations and credentials in AtomIQ before calling tools that access mainframe systems. AI-dependent tools require an AI provider in workspace settings.
Connect AI assistants to AtomIQ’s MCP server, including remote host URLs.