HermetiqDocsOpen dashboard
MCP and AI agents
MCP and AI agents

Connect Hermetiq to your AI agent

Install the Hermetiq skill and MCP server for Claude Code, Claude Desktop, Cursor, Windsurf, or Codex, then query real build data.

Clients: Claude Code · Claude Desktop · Cursor · Windsurf · Codex

Prerequisites

You need access to a Hermetiq project receiving BEP events. Sign in to the matching Cloud or customer-managed dashboard before the first MCP authentication flow.

The Hermetiq AI plugin combines the remote MCP server with a Bazel and Buildbarn skill that guides the agent toward the appropriate build, cache, profile, RBE, cost, test, or infrastructure queries.

Claude Code

Add the Hermetiq plugin marketplace, then install the plugin:

Claude Code
/plugin marketplace add Hermetiq/hermetiq-ai-plugin
/plugin install hermetiq@hermetiq

The plugin configures the MCP server. On first use, follow the authentication flow for your Hermetiq account. Use /mcp to re-authenticate if the connection expires or is denied.

Open the Hermetiq AI plugin repository →

Claude Desktop

For an individual account, open Customize → Connectors, add a custom connector, and enter https://mcp.cloud-usc1.hermetiq.io. Team and Enterprise owners manage organization connectors under the organization’s settings.

Package the plugins/hermetiq/skills/hermetiq directory from the plugin repository as a ZIP and upload it under Customize → Skills.

Review Claude connector instructions →

Cursor and Windsurf

Both clients accept an HTTP MCP server entry. Use the project’s Quickstart-generated endpoint when it differs from Hermetiq Cloud.

.cursor/mcp.json or ~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "hermetiq": {
      "type": "http",
      "url": "https://mcp.cloud-usc1.hermetiq.io"
    }
  }
}

After saving the file, reload the client, enable the Hermetiq server, and complete the browser OAuth flow. Install the Hermetiq skill separately if the client supports reusable agent instructions.

Codex

Add the remote MCP server, authenticate, and verify the saved configuration:

Terminal · MCP
codex mcp add hermetiq --url https://mcp.cloud-usc1.hermetiq.io
codex mcp login hermetiq
codex mcp get hermetiq

Then install the current Hermetiq skill at the repository scope so teammates can review and share the same instructions:

Terminal · from your repository root
git clone https://github.com/Hermetiq/hermetiq-ai-plugin
mkdir -p .agents/skills
cp -R hermetiq-ai-plugin/plugins/hermetiq/skills/hermetiq .agents/skills/hermetiq

Codex detects skills in .agents/skills automatically. Start a new session after installation; restart Codex only if the skill does not appear.

Available workflows

The server exposes guided prompts as well as lower-level tools. Availability can vary with the project’s data sources and server configuration.

debug_cache_missesanalyze_invocationinvocation_insightsinvestigate_failurediagnose_exec_environmenttest_failuresproject_healthcost_analysisfind_slow_buildsweekly_trends_reportcache_trendsprofile_trendsrbe_trendsrbe_optimizationcompare_periodsinfra_healthanalyze_storage_configsetup_hermetiq_bazel

Natural-language requests work too: “Why did my latest build slow down?”, “Show cache-miss trends for the last seven days,” or “Which targets are most expensive to execute remotely?”

Prompts are guided workflow templates rather than tools. Lower-level tools and resources remain available for questions that do not map to one prompt.

AI-assisted Bazel setup

Hermetiq Cloud Quickstart can expose a Beta step that asks an MCP-connected agent to configure the current Bazel workspace. Download and secure the project credential helper first, then give the agent an explicit repository path.

Example request
Add the Hermetiq config group with remote cache enabled for my Bazel project in: <directory>

The agent uses setup_hermetiq_bazel and the project’s MCP Quickstart data to propose or apply the matching .bazelrc configuration. Review the diff before committing it.

Customer-managed endpoint

The plugin defaults to Hermetiq Cloud. Customer-managed deployments can point the plugin or MCP client at that deployment’s MCP endpoint.

Environment
export HERMETIQ_MCP_URL=https://mcp.hermetiq.your-domain.example

For manual clients, replace the cloud URL in the MCP configuration with the customer-managed endpoint and authenticate through that deployment’s configured identity provider. Do not sign in through the hosted dashboard unless your administrator specifically directs you there.

Last reviewedSeptember 1, 2026