Hiveclaw

io.github.omiiyamuPublished by GitHub account omiiyamuv0.1.1Updated Oct 24, 2026

Connect AI assistants to HiveClaw — manage projects, talk to AI agents, and more.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Hiveclaw connects an AI assistant to the HiveClaw platform so it can manage projects and talk to AI agents.

What you can do
Manage HiveClaw projects from the assistant, according to the provider's description of project management and other platform actions. Interact with AI agents hosted on HiveClaw. The provider does not publish a tool list, so the exact actions available are not documented here.
When to use it
Worth considering if you already use HiveClaw and want an assistant to work with your projects and agents there without switching tools. Less useful if you do not have a HiveClaw account or need a documented, predictable set of tools.
Requirements
A HiveClaw account and an API key supplied as HIVECLAW_API_KEY (starts with hc_); OAuth authentication is also declared. Can run as a remote endpoint or as a local npm package over stdio. The optional HIVECLAW_API_URL variable overrides the default API base URL. Network access to the HiveClaw API is required.
Before you install
The server requires a HiveClaw API key, a credential that grants access to your account; keep it private and scope it as narrowly as the platform allows. It can change data in your HiveClaw projects and send prompts to hosted AI agents, so review actions before letting an assistant run them. Project and agent content is sent to HiveClaw's servers.

Installation

In SourceWeft

  1. Open Hiveclaw 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/io.github.omiiyamu%2Fhiveclaw/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": {
    "hiveclaw": {
      "type": "http",
      "url": "https://api.hiveclaw.ai/api/v1/mcp/remote"
    }
  }
}

README

This repository has no README.

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. v0.1.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.