BrinqaIQ MCP
BrinqaIQ's Model Context Protocol (MCP) integration lets you connect any MCP-compatible AI client — such as Claude Desktop, Cursor, or GitHub Copilot in VS Code — directly to your Brinqa Platform over HTTP. There is no local server to run and no Python wrapper to install: you point the client at a single URL with your API token.
What is MCP?
MCP is an open standard that lets AI applications connect to external data sources and tools through a standardized interface. By implementing MCP, BrinqaIQ enables MCP-compatible AI clients to interact with BrinqaIQ capabilities — writing and executing BQL queries, exploring CVEs, managing flows and automations, creating remediation tickets from findings, and searching documentation — without leaving your existing tooling.
BrinqaIQ MCP exposes 30 tools. For the full tool list, annotations, and capability deep dives, see the Tools Reference.
Security and access control
BrinqaIQ MCP uses API token authentication. Each request includes an Authorization: ApiKey <token> header. The token authenticates your MCP client with the Brinqa Platform; no other Brinqa Platform APIs are reachable through this surface.
To generate a token, see API Token Authentication.
All tool invocations inherit the permissions of the user account that issued the API token, including role-based and data-level access controls. MCP can only access data that the user already has permission to view in the Brinqa Platform UI.
The setup steps below require Brinqa Platform 12.3 or later, which exposes the Streamable HTTP MCP endpoint at /brinqamax/mcp. If you are on an earlier version, follow the v11 version of this page for the legacy OpenAPI-proxy configuration with bearer authentication.
For the connection pattern and per-client setup instructions, see Supported Clients.