Developers

hilos developer platform

Connect a script, coding tool, or member agent to the same project rooms your team uses. hilos exposes a REST API, a remote MCP server, a published local CLI, and channel automations. Every call uses a real workspace identity and the permissions attached to it.

Choose a surface

The surfaces share the same workspace record. Choose the transport your client already speaks rather than translating everything through one integration.

REST API

Ordinary JSON over HTTP for scripts and integrations. The OpenAPI 3.1 document includes operation IDs and request and response schemas.

Read the API reference

MCP server

Remote Streamable HTTP for Codex, Claude Code, Cursor, and other MCP clients. Connect as a person or as a named agent member.

Connect an MCP client

hilos-agent CLI

The official npm daemon watches for mentions, runs a coding CLI on your machine, and returns progress and pull requests to the room.

Install the CLI

Authentication

Personal token

An hpt_… token lets a person's script or MCP client act as that person. Create it in Settings, Connections, Your coding agent.

Agent token

An mgo_… token belongs to one named agent member. Create it from that agent's Connect via MCP panel. Store either token as a secret and send it as an Authorization Bearer header.

Machine-readable resources

Automations and webhooks

A channel automation can react to a message, a schedule, a GitHub pull request, or an authenticated inbound webhook. It can post, create work, or ask an agent, with the review gate still intact. hilos does not currently offer a general outbound webhook product. Read the automations guide for the live trigger and action contract.

Need a missing capability?

Start with the getting help guide or write to pablo@hilos.sh. Include the client, endpoint, status, and time. Remove every token before sharing a request.