Skip to main content

colabhive-mcp

Model Context Protocol (MCP) server that exposes ColabHive models — LLMs, specialists, tools and your trained models — to MCP-compatible clients such as Claude Desktop, Claude Code, Cursor and n8n.

User docs: https://docs.colabhive.com/mcp

Install

# Recommended (no global Python needed)
uvx colabhive-mcp

# Or pipx
pipx install colabhive-mcp

# Or pip (Python 3.10+)
pip install colabhive-mcp

Quickstart

Create an API key in the ColabHive Console (Settings → API Keys); keys start with hive_.

export COLABHIVE_API_KEY=hive_...
colabhive-mcp test

Then add the server to your MCP client:

{
  "mcpServers": {
    "colabhive": {
      "command": "uvx",
      "args": ["colabhive-mcp"],
      "env": { "COLABHIVE_API_KEY": "hive_..." }
    }
  }
}

A hosted server is also available at https://mcp.colabhive.com. See the user docs for per-client guides.

colabhive-mcp sdk-stdio and colabhive-mcp sdk-serve provide strict stdio and stateless Streamable HTTP transports built on the official MCP Python SDK, alongside the default stdio and HTTP/SSE transports.

Built-in account tools

  • get_account_preferences and set_share_hive_opt_in read and set the account-scoped Share Hive preference. The credential selects the account; only the account owner can write it.
  • get_effective_data_protection and preflight_data_protection read the effective node-eligibility policy and preflight a placement. There is no policy-mutation tool.
  • get_memory_status reads whether memory is on for the account (enabled) and whether a task would carry it right now (ready), with detail naming what is unfinished when the two disagree. Memory is enabled per account and the platform ties the binding, so there is no namespace, snapshot or binding tool.

Experimental Cohort tools

Six opt-in tools (cohort_capabilities, plan_cohort, run_cohort, get_cohort, explain_cohort, cancel_cohort) stay hidden unless COLABHIVE_MCP_COHORT_TOOLS_ENABLED=true, MCP stability permits experimental tools, the account has Cohort capability, and the kind and side-effect filters allow the operation.

License

MIT — see LICENSE.

Metadata

Release files for colabhive-mcp 0.3.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for colabhive-mcp 0.3.4
File Size Uploaded Provenance Actions
colabhive_mcp-0.3.4.tar.gz 48.9 kB Without provenance Details for colabhive_mcp-0.3.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for colabhive-mcp 0.3.4
File Interpreter ABI Platform Actions
colabhive_mcp-0.3.4-py3-none-any.whl Python 3 none any Details for colabhive_mcp-0.3.4-py3-none-any.whl

Total release size: 88.4 kB

Release files / colabhive_mcp-0.3.4.tar.gz

Download URL colabhive_mcp-0.3.4.tar.gz
Size 48.9 kB
Tags Source
SHA-256 checksum
How to use checksums
132620f41f1a4973fef4064d4b090ae3df6d8e40f6697f3000f07d4d59180a0a
BLAKE2b-256 checksum
How to use checksums
42763a27c5e5d81087865e83ded379ae6046dac37a90096e73ab4cd7659641e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / colabhive_mcp-0.3.4-py3-none-any.whl

Download URL colabhive_mcp-0.3.4-py3-none-any.whl
Size 39.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a1d1712d11c18bc1903395d4ac66f2df33cc05327a15be6c6683473621fa6537
BLAKE2b-256 checksum
How to use checksums
5aaa2d409d8d1695bcd6608c127ff987feed75e568554dcc2108904f9cf40065
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for colabhive-mcp 0.3.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page