Skip to main content
VisIQ exposes an authenticated Model Context Protocol (MCP) server so an AI agent or MCP-capable client can operate the product with tool calls instead of raw REST. It is the same management surface as the web app and the automation API — every tool enforces the identical RBAC permission its web route requires.
There are two VisIQ MCP servers, both listed in /.well-known/mcp/server-cards.json:
  • Public MCP — https://visiqlabs.com/mcp — read-only discovery, no credentials. Public information about VisIQ only.
  • Platform MCP (this page) — https://app.visiqlabs.com/api/mcp — authenticated; operates your tenant.

​
Endpoint & transport

You need a management-audience API key. Get one from Connectors → API Keys in the dashboard, or have your agent self-register with "requested_key_type": "management". A harness key is confined to the SDK operational surface and is not accepted here.
The server is fail-closed: a missing or invalid key is rejected, and a tool whose required permission the key does not hold returns an error naming the missing permission (never a silent partial result). Nothing is anonymously accessible.

​
Connect a client

Point any MCP client at the endpoint with a bearer header. For example, a generic mcpServers configuration:
Then start with whoami to confirm which vendor and permissions your key resolves to — every other tool is gated by those permissions.

​
Tool catalog

The server advertises the tools below via tools/list. Each is permission-gated exactly like its web/API counterpart. Discovery
  • whoami — the vendor and effective permissions your key holds. Call this first.
  • describe_chat — how the in-product natural-language query tools work.
Action governance (rules)
  • list_rules, get_rule — read action rules
  • create_rule, update_rule, delete_rule — author action rules
  • compile_rule — compile natural language into a rule (requires allow_rules:create or recall_rules:create)
Retrieval governance (rules)
  • list_recall_rules, create_recall_rule — read and author retrieval rules
Agents
  • list_agents, get_agent — inventory
  • register_agent, update_agent — register and manage agents across frameworks
Decisions & schemas
  • get_decision_outcomes — decision/audit outcomes
  • list_action_schemas — the action schemas agents report
Human-in-the-loop
  • list_hitl_queue — pending approvals
  • respond_hitl — approve or deny a queued action (authenticated approver identity)
Settings
  • get_allow_settings, update_allow_settings — enforcement mode and settings
Natural-language queries
  • chat_rules_table, chat_events_log, chat_agents_inventory, chat_hitl_queue, chat_data_table — ask questions over each surface in plain language
Key lifecycle
  • revoke_self — revoke this key (no arguments, no permission required). It stops authenticating immediately, so make it your final call. See self-revocation.