Hlix

ai.hlixPublished by hlix.aiOfficial publisherv0.5.0Updated Nov 12, 2026

Build software with your Hlix cloud team: start work, check progress, preview, review and ship.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Hlix is a remote MCP server that lets an assistant start, track, preview, review and ship software work with a cloud team.

What you can do
  • Start development work with a Hlix cloud team
  • Check the progress of ongoing work
  • Preview and review results before release
  • Ship finished work
When to use it
Useful if you already work with a Hlix cloud team and want an assistant to kick off tasks, follow their progress, and move them through preview, review and shipping without leaving the chat.
Requirements
A remote MCP endpoint at mcp.hlix.ai over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
The server can start, review and ship software work, so actions may change or release code in your Hlix projects. Access is granted through OAuth to your Hlix account; review what the connected client is permitted to do before authorizing.

Installation

In SourceWeft

  1. Open Hlix in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.hlix%2Fhlix/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.5.0LatestNov 12, 2026
  2. v0.4.0Sep 29, 2026
  3. v0.3.0Sep 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Hlix integrations