Breadcrumbs

MCP

HALO provides a Model Context Protocol (MCP) server. MCP clients such as Claude, ChatGPT, and Codex can use it to create and update agents, build tools, manage context variables, and review conversations in natural language.

Property

Value

URL

https://api.cm.com/halo/mcp

Transport

Streamable HTTP

Authentication

OAuth 2.1 with CIMD (Client ID Metadata Documents)

When you connect, your client opens a browser window. There, you sign in to CM.com, choose a HALO account and profile, and approve access.

Before you start: you need a CM.com login with access to HALO Studio. Your client must support remote MCP servers with OAuth and CIMD. Clients that only support Dynamic Client Registration (DCR) can't complete this flow; use Header authentication at the end of this page instead.

Connect from Claude (web and desktop)

The steps are the same on claude.ai and in the Claude desktop app.

On Claude Team or Enterprise plans, you may not be able to add connectors yourself; an admin has to make the connector available to your organization first. Once they've added HALO, find it under Customize → Connectors, choose Connect, and continue from step 4.

  1. Open Customize → Connectors and choose Add custom connector.

    Screenshot 2026-09-29 at 13.55.40.png

  2. Enter a name, such as HALO, and the URL https://api.cm.com/halo/mcp, then choose Add.

    Screenshot 2026-09-29 at 13.56.13.png

  3. Choose Continue.

  4. Sign in to CM.com if prompted. On the consent page, select the account and profile, then approve.

Connect from ChatGPT (web and desktop)

ChatGPT adds MCP servers as custom apps, which requires Developer mode.

You need a paid ChatGPT plan that supports Developer mode. On workspace plans, an admin may need to enable Developer mode first or make the connector avaialbe to you.

  1. Open Settings → Plugins → Advanced settings and turn on Developer mode.

  2. Go back to Plugins and choose Add → Create MCP App.

    Screenshot 2026-09-29 at 14.04.53.png

  3. Enter a name, such as HALO, and the URL https://api.cm.com/halo/mcp, and set Authentication to OAuth.

    Screenshot 2026-09-29 at 14.05.41.png

  4. Tick I understand and want to continue, then choose Create. Sign in to CM.com if prompted. On the consent page, select the account and profile, then approve.

Connect from Claude Code

  1. Add the server:

 claude mcp add --transport http halo https://api.cm.com/halo/mcp

  1. Start Claude Code, run /mcp, select halo and choose Authenticate.

  2. Sign in to CM.com if prompted. On the HALO consent page, select the account and profile, then approve.

Connect from Codex CLI

  1. Add the server and log in:

 codex mcp add halo --url https://api.cm.com/halo/mcp
 codex mcp login halo

  1. Sign in to CM.com if prompted. On the consent page, select the account and profile, then approve.

Other clients

Any other client that supports remote MCP servers with OAuth and CIMD can connect. Add https://api.cm.com/halo/mcp as a remote server using Streamable HTTP, then complete the browser authorization.

Ask your agent to set it up

If your coding agent can edit its own MCP configuration, ask it:

Add the HALO MCP server at https://api.cm.com/halo/mcp using Streamable HTTP. Use OAuth and let me complete the browser authorization. Show me the configuration before saving it.

E-learning

This video demonstrates the new HALO MCP, a tool that lets you connect HALO to Claude, Codex, or any other MCP-compatible client. You'll see how to create and update agents, wire up tools, and manage MCP server connections, all via natural-language requests rather than manual configuration. The video also shows how to analyze existing conversations to spot gaps or missing tools, then patch an agent on the spot. It's a practical walkthrough of how HALO MCP accelerates agent development and debugging.

Header authentication

For clients that can't use OAuth with CIMD but do support custom HTTP headers, use the same URL with these headers:

Header

Value

X-CM-PRODUCTTOKEN

An MCP token from Settings > Product Tokens in HALO Studio

CM-ACCOUNT-ID

Your CM.com account ID, shown in the HALO Studio URL

CM-PROFILE-ID

Your HALO profile ID, shown in the HALO Studio URL

For example, in Claude Code:

claude mcp add --transport http halo https://api.cm.com/halo/mcp \
  --header "X-CM-PRODUCTTOKEN: <token>" \
  --header "CM-ACCOUNT-ID: <account-id>" \
  --header "CM-PROFILE-ID: <profile-id>"

Treat the product token like a password: don't commit it to source control, and use environment variables where your client supports them. The old URL https://api.cm.com/halo/core/mcp is now deprecated but still operational.