Skip to content

MCP server

Give AI platforms direct access to Array HQ capabilities through the Model Context Protocol.

The operational problem

AI platforms can analyze data and automate workflows — but only if they can reach the systems where that data lives. Without a standard way to connect, every AI integration requires custom scripting, manual data exports, or one-off API wrappers. Each new AI tool means another integration project.

How Array HQ solves it

The Array HQ MCP server exposes platform capabilities through the Model Context Protocol (MCP) — an open standard that AI platforms use to discover and invoke tools. Connect your AI platform once, and it can query metrics, explore organizational data, and interact with Array HQ directly.

The server controls what each user can see and do. Tools are composed based on your permissions, so users only access the capabilities they're authorized to use.

How it works

Connecting an AI platform

AI platforms that support MCP (such as Claude, OpenAI, and others) connect to the Array HQ MCP server at its public endpoint. The connection uses the standard MCP protocol — no custom SDK or client library is required.

Authentication

The MCP server uses OIDC authentication through auth.arraycorp.com — the same identity provider used across Array HQ. When an AI platform connects:

  1. The user authenticates through the standard login flow
  2. The MCP server validates the session against the identity provider
  3. Tools are composed based on the authenticated user's permissions

This means the AI platform operates with the same access boundaries as the user — it cannot see or do anything the user couldn't do themselves through the standard interface.

Authorization-aware tools

Not every user sees every tool. The MCP server checks which capabilities are granted to the authenticated user and only exposes the tools they're authorized to use. This is based on the same permission policies that govern the rest of Array HQ.

If a user has access to operational metrics but not to member management, the AI platform connected on their behalf will see metric tools but not member tools.

Available tools

The MCP server exposes platform capabilities as individual tools that AI platforms can discover and invoke:

Tool What it does
get_organization_units Retrieve the organizational structure — accounts, organizations, and hierarchy
get_metric_definitions List available metric definitions configured for your organization
get_metric_definition Get details for a specific metric — what it measures, how it's calculated
get_metric_results Query metric results with filtering by organization, time range, and aggregation level

Additional tools are added as platform capabilities expand. The AI platform discovers available tools automatically through the MCP protocol — no configuration changes are needed when new tools become available.

What you can build

With MCP access, AI platforms can:

  • Query workforce metrics — ask natural-language questions about operational performance across sites and time periods
  • Analyze trends — compare goal attainment, productivity, or staffing levels across organizations without manual data exports
  • Build reports — generate operational summaries by pulling real-time data directly from Array HQ
  • Automate analysis — set up recurring AI-driven reviews of metrics that surface signals and anomalies

Key terms

Term Meaning
MCP (Model Context Protocol) An open standard that AI platforms use to discover and invoke tools from external services.
MCP server The Array HQ service that exposes platform capabilities to AI platforms through MCP.
Tool A specific capability exposed through the MCP server — such as querying metrics or listing organizations.
OIDC OpenID Connect — the authentication protocol used to verify user identity when connecting AI platforms.
Authorization-aware composition The process of showing each user only the tools they have permission to use.