MCP

HAL exposes a hosted HTTP MCP endpoint for external AI clients.

Use MCP when Claude, Cursor, or another compatible client should work with HAL project data through tools. HAL does not provide a local stdio server.

Endpoint

POST https://api.chatwithhal.com/mcp

Authentication

Use an account-scoped MCP key from Settings → API. Clients should call list_projects first, then include project_id or project_slug for project-scoped tools.

Example config

{
  "mcpServers": {
    "hal": {
      "type": "streamable-http",
      "url": "https://api.chatwithhal.com/mcp",
      "headers": {
        "X-API-Key": "YOUR_HAL_ACCOUNT_MCP_KEY"
      }
    }
  }
}

What the endpoint can do

Read projects and conversations

List projects, inspect conversations, and use customer context without rebuilding the model outside HAL.

Work with CRM and knowledge

Read or update company records, articles, groups, and other structured project data through tools.

Stay within HAL boundaries

MCP gives AI clients access to HAL. It does not turn HAL into an unsupervised external execution layer.

Operational notes

HTTP only. There is no local MCP transport to install.
Project-scoped tools require explicit project selection.
Missing or partial Accept headers are normalized for plain HTTP clients.

Related docs

Use MCP for AI clients and the API for direct app integrations.

REST API Operator loop