Connect your AI

Use your AI assistant to work with your Hlix team. Connect once, then ask about a project, request a change or inspect the result.

https://mcp.hlix.ai/mcp

Interactive clients sign in through your browser. Scripts and CI use an API key. To give an agent documentation and local CLI guidance as well, see Set up your agent.

Sign in with Hlix

1. Add the hosted URL to your assistant using the setup below.
2. Sign in, allow all your Workspaces or select specific ones, and choose read-only or read-and-write access.
3. Ask: “Use Hlix to show my Workspace and list my projects.”

The assistant can use hlix_whoami to confirm its accessible Workspaces and default selection, then hlix_projects to find the right project. An OAuth connection can reach all your Workspaces or the set you selected, with your current role in each. Pass the intended Workspace when the default is not the one you want. Read-and-write access adds tools that start or change work; it does not expand your project permissions.

Connect your AI

Claude

In Claude, add the URL as a custom connector under Settings → Connectors and sign in. The connection is associated with your Claude account. Claude’s connector guide covers the current setup flow.

Claude Desktop

Use the same account connector added in Claude.

ChatGPT

Create a custom MCP app in ChatGPT’s Apps settings, enable developer mode and enter the URL. Follow OpenAI’s developer-mode guide for your Workspace’s setup controls.

Cursor

Add to Cursor, then sign in when prompted.

VS Code

Add to VS Code, then sign in when prompted.

Claude Code

claude mcp add --transport http hlix https://mcp.hlix.ai/mcp

Run /mcp in Claude Code and choose Hlix to sign in. The optional Hlix plugin adds the same server and a skill for the project workflow:

/plugin marketplace add hlix-ai/claude-plugins
/plugin install hlix@hlix

Codex

codex mcp add hlix --url https://mcp.hlix.ai/mcp
codex mcp login hlix

Gemini CLI

gemini mcp add --transport http hlix https://mcp.hlix.ai/mcp

Gemini CLI asks you to sign in when it first uses the connection.

Antigravity

Open Antigravity’s MCP configuration and add the hosted server using serverUrl:

{"mcpServers":{"hlix":{"serverUrl":"https://mcp.hlix.ai/mcp"}}}

Other clients

Use the remote-server format your client supports. A common configuration is:

{"mcpServers":{"hlix":{"url":"https://mcp.hlix.ai/mcp"}}}

The Hlix dashboard’s Connect your AI page provides these setup actions with your environment’s URL.

Start with an existing project

Ask your assistant to find the project and check its current status before choosing what to do next:

Use Hlix to find the Acme storefront project and summarize its status, pending questions and latest review results.

Then request the work you want:

Add keyboard navigation to the product filters in that project, with tests. Keep the existing visual design.

hlix_build starts billable project work. Projects using an initial proposal wait for the required agency approval before the first build agent starts. The team then works in the cloud; the assistant can check progress with hlix_status without keeping the conversation open. A status check no more than once a minute is sufficient.

Use hlix_review to inspect results and hlix_preview to get the preview. hlix_deliver prepares a pull request, then requires its confirmation step before opening it. It never merges. See the full tool catalog for inputs, access and provider actions.

For scripts and CI

Use the same endpoint with a Hlix API key. Store the key outside committed configuration. These examples read HLIX_API_KEY from the environment.

Authorization: Bearer <your API key>

X-API-Key: <your API key> also works. A key acts as its creator across the Workspaces they belong to, with their current role in each. Pass a Workspace name or ID when the default is not the one you intend. API-key connections can discover read and write tools; each action still checks permissions.

Claude Code

claude mcp add --transport http hlix https://mcp.hlix.ai/mcp --header "Authorization: Bearer $HLIX_API_KEY"

Codex

codex mcp add hlix --url https://mcp.hlix.ai/mcp --bearer-token-env-var HLIX_API_KEY

Or configure ~/.codex/config.toml:

[mcp_servers.hlix]
url = "https://mcp.hlix.ai/mcp"
bearer_token_env_var = "HLIX_API_KEY"

Other clients

{"mcpServers":{"hlix":{"type":"http","url":"https://mcp.hlix.ai/mcp","headers":{"Authorization":"Bearer <your API key>"}}}}

Revoke access

Remove or disconnect Hlix in your assistant’s MCP or app settings. For command-line clients:

claude mcp remove hlix
codex mcp logout hlix
codex mcp remove hlix
gemini mcp remove hlix

For the Claude Code plugin, use /plugin uninstall hlix@hlix. Delete an API key in Developer tools → API keys to revoke it. Removing a member from a Workspace also ends that person’s access on the next call.

Troubleshooting

• Sign-in does not open. In Claude Code, run /mcp and choose Hlix. In Codex, run codex mcp login hlix.
• Wrong Workspace. Ask the assistant to run hlix_whoami, then pass the intended Workspace. If an OAuth grant does not include it, reconnect to change the allowed Workspaces.
• Write tools are missing. Reconnect with read-and-write access if the assistant needs to make changes. Its actions remain limited by your role.
• Several projects match. Choose the intended project from the returned candidates.

For provider actions, funding, mailbox orders and external connections, use MCP tools. These are separate from connecting your assistant to Hlix.

Next steps

Set up your agent

Give an assistant documentation, the API contract and CLI guidance.

MCP tools

Browse the complete tool catalog and read/write boundaries.

Reviewing output

Inspect delivered changes and their review evidence.