hilos workspace

sh.hilosPublished by hilos.shOfficial publisherv1.0.2Updated Oct 24, 2026

Operate hilos project rooms, Docs, Tasks, messages, memory, and coding-agent review workflows.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A remote MCP server that lets an assistant operate hilos project rooms, including Docs, Tasks, messages, memory and coding-agent review workflows.

What you can do
Work with hilos project rooms and their contents from the assistant. Manage Docs and Tasks inside a room. Read and post messages. Use stored memory as context. Support coding-agent review workflows.
When to use it
Useful when your team runs projects in hilos and you want an assistant to work with room Docs, Tasks, messages and memory, or to help with coding-agent review, without leaving the conversation.
Requirements
A remote streamable HTTP endpoint at hilos.sh; no local package or runtime is needed. A hilos account and a bearer token sent in the Authorization header are required.
Before you install
The server requires a bearer token in the Authorization header, so treat that credential as sensitive. It can read and change project room content such as Docs, Tasks and messages, and it stores memory, so review what the assistant writes or sends before relying on it.

Installation

In SourceWeft

  1. Open hilos workspace in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/sh.hilos%2Fworkspace/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.

{
  "mcpServers": {
    "hilos-workspace": {
      "type": "http",
      "url": "https://hilos.sh/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.2LatestSep 16, 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.