MCP introduction

Hyax runs a stateless Streamable HTTP MCP server at POST /hyax-api/mcp. Connect Cursor, Claude, Claude Code, Codex, or any MCP-compatible agent. Clients that support sign-in (OAuth 2.1 with dynamic registration, e.g. Claude custom connectors) only need the URL: the person signs in to Hyax, picks a team and chooses what the agent may do. Other clients send a team API key (Authorization: Bearer hx_…). Keys and connections carry permissions (read, create and edit, delete, send, paid AI, connections and bulk data), set under Settings → Team → API. Besides the dedicated tools, app_list_actions / app_describe_action / app_read / app_change reach the rest of the Hyax app; billing, API keys, team members and payout settings are never available to agents. The server exposes JSON-RPC 2.0 methods (initialize, tools/list, tools/call) over HTTP POST. GET requests return 405.

Base URL: https://platform.hyax.com · Replace YOUR_API_KEY with your team API key.

# This route is session-based, multipart, or provider-specific.
# Inspect: apps/web/server/routes/hyax-api/

// Cursor / Claude Desktop (streamable HTTP)
{
  "url": "https://your-domain.com/hyax-api/mcp",
  "headers": {
    "Authorization": "Bearer hx_your_api_key"
  }
}

// Claude Desktop mcpServers config (claude_desktop_config.json)
{
  "mcpServers": {
    "hyax": {
      "url": "https://your-domain.com/hyax-api/mcp",
      "headers": {
        "Authorization": "Bearer hx_your_api_key"
      }
    }
  }
}