Hydite Mcp
Connect your local MCP client to Hydite services over stdio via the published @hydite/hydite-mcp npm package.
Overview
io.github.Aiomx/hydite-mcp is a Build-phase MCP server delivered as @hydite/hydite-mcp over stdio with a required Hydite secret for Hydite platform integration.
What is this MCP server?
- npm package @hydite/hydite-mcp at version 1.0.2
- stdio transport for local Claude Code, Cursor, and compatible hosts
- Required secret environment variable Hydite (string, marked isSecret)
- GitHub source at github.com/Aiomx/hydite-mcp
- MCP server name io.github.Aiomx/hydite-mcp in official schema
- Package version 1.0.2
- Transport: stdio
- npm identifier: @hydite/hydite-mcp
What problem does it solve?
You have Hydite access but your coding agent cannot call Hydite workflows until a stdio MCP package and credential are wired up locally.
Who is it for?
Solo builders already on Hydite who prefer local stdio MCP over remote HTTP and have the Hydite API or license string ready.
Skip if: Builders without Hydite credentials, teams needing hosted streamable-http MCP only, or anyone expecting documented tool lists solely from the sparse catalog blurb.
What do I get? / Deliverables
After npm install and Hydite env configuration, your MCP client can invoke Hydite-backed tools from the repository-defined server.
- Installed @hydite/hydite-mcp package at version 1.0.2 or compatible
- Configured stdio MCP server entry with Hydite secret
- Agent session able to list and call Hydite MCP tools from the GitHub project
Recommended MCP Servers
Journey fit
Hydite ships as an npm MCP bridge during product construction, so the canonical shelf is build-phase integrations. Stdio npm packaging signals a developer integration you install beside the agent rather than a launch or growth distribution tool.
How it compares
Vendor-specific stdio npm MCP bridge, not an Ainode x402 remote utility bundle.
Common Questions / FAQ
Who is io.github.Aiomx/hydite-mcp for?
It is for developers using Hydite who want Claude Code, Cursor, or other stdio MCP clients to reach Hydite through @hydite/hydite-mcp.
When should I use io.github.Aiomx/hydite-mcp?
Use it during build when you are integrating Hydite into an agent workflow and can supply the required Hydite secret environment variable.
How do I add io.github.Aiomx/hydite-mcp to my agent?
Install @hydite/hydite-mcp from npm, set the Hydite secret env var per registry metadata, and add a stdio MCP server entry pointing at that package in your agent config.