Hythe MCP Server

Hythe is an MCP integration. HYTHE — coordination bus + shared truth for AI agent fleets — self-hosted MCP server + stdio bridge.

Packages and local setup

The published npm package is @hythe/mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares HYTHE_AGENT_ID (required): Stable exact agent identity for this client lane; required so restarts and compaction cannot adopt another principal; HYTHE_AGENT_KEY_FILE: Optional path to one protected per-agent credential file: regular, non-symlink, owned by the client user, mode 0400 or 0600, containing one hya1 token. Never place the token itself in an environment variable.; HYTHE_AGENT_AUTH_MODE: Client authorization expectation: observe, mixed, or required (default observe). Move to mixed and then required only after this exact lane has a credential and passes /agent/whoami.; API_KEY (required): Shared API key authenticating the bridge to your self-hosted HYTHE server (create a protected .env with: npx -y @hythe/mcp@0.2.0 init --write-env --agent-id ); MCP_HOST: HYTHE server host (default 127.0.0.1); MCP_PORT: HYTHE server port (default 6174).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.