BlueCat Integrity is automatable through its API

BlueCat Integrity is automatable today through the Address Manager RESTful v2 API. Integrity is the DDI platform for DNS, DHCP, and IP address management. The product page says it runs across cloud, on-premises, and hybrid networks and publishes a RESTful OpenAPI. The 26.1.0 API guide says the OpenAPI document is at http://{Address_Manager_IP}/api/openapi.json. A client creates a session with POST /api/v2/sessions and a JSON username and password. The response includes apiToken and basicAuthenticationCredentials. Later calls send Authorization Basic with that encoded username and token. The same guide documents OAuth 2.0 bearer tokens, configured in the Address Manager UI or through /api/v2/authenticators. The product page also says Integrity ships Python libraries and works with Ansible, Terraform, and ServiceNow, and that JSON and CSV can both be exported and imported. BlueCat's 26.1.0 Integrity MCP Server Tool Reference documents API-derived tools that read Address Manager collections. Those tools are read-only. User, user-group, access-right, and session collections are redacted, and getUsers is not registered. The pagination page says workflow tools allow roughly 240 seconds, so workflows exist beside the read-only lookups. This pass did not open a catalog of those workflow tools. The registry row com.bluecat/integritymcp, version 26.1.0, updated 2026-09-24, is the image quay.io/bluecat/integritymcp listening on http://localhost:9998/mcp. It requires a BlueCat Address Manager URL, either a service-account username and password or an SSO username and password, an MCP client authentication mode, and acceptance of the BlueCat end user license. An environment note on that row mentions approval-gated write tools. The 10 September 2026 BlueCat post still names LiveNX and LiveWire as the initial supported MCP servers and says coverage will expand. It does not name Integrity. The tool reference is the BlueCat page that documents the Integrity MCP server, so the server is first-party. Connector catalogs were not opened. Computer-use viability is unassessed. The API scores 7. The MCP server scores 6 because the opened tool reference is a read-only lookup layer on a customer-hosted Address Manager. The API is the best path.

Best path today: api · Overall automatability: 7/10