MCP server
The hivepod CLI includes an MCP server, so AI coding tools can deploy your code and manage your DockHive resources for you. Ask your assistant something like “Deploy this folder to DockHive” and it uses Drone to get it live.
Before you start
Section titled “Before you start”- Install the CLI.
- Sign in:
hivepod login. The MCP server uses this sign-in (orHIVEPODS_TOKEN, if set).
Add it to your tool
Section titled “Add it to your tool”Run hivepod mcp --print-config to print ready-made snippets with the full path to hivepod filled in.
claude mcp add dockhive -- hivepod mcpTo make it available in every project:
claude mcp add --scope user dockhive -- hivepod mcpIf hivepod isn’t on your PATH, use its full path, for example ~/.hivepods/bin/hivepod.
Add this to ~/.cursor/mcp.json:
{ "mcpServers": { "dockhive": { "command": "/Users/you/.hivepods/bin/hivepod", "args": ["mcp"] } }}Open Settings → Developer → Edit Config and add to claude_desktop_config.json:
{ "mcpServers": { "dockhive": { "command": "/Users/you/.hivepods/bin/hivepod", "args": ["mcp"] } }}Add this to ~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "dockhive": { "command": "/Users/you/.hivepods/bin/hivepod", "args": ["mcp"] } }}Desktop apps don’t see your shell’s PATH, so use the full path to hivepod. With the installer it’s ~/.hivepods/bin/hivepod on macOS and Linux, and %USERPROFILE%\.hivepods\cli\Scripts\hivepod.exe on Windows. Any other MCP client that can run a local stdio server works the same way.
| Tool | What it does |
|---|---|
deploy |
Deploy a folder or a GitHub repository with Drone and return the live URL. |
deployment_status |
Status, URL and Drone’s progress for a deployment. |
build_logs |
A deployment’s build log. |
list_apps |
Your apps with their addresses, regions and domains. |
app_logs |
An app’s runtime logs. |
set_env |
Set or unset environment variables (values are write-only), optionally redeploying. |
redeploy |
Rebuild an app from its repository. |
rollback |
Put an earlier version back live. |
add_domain, domain_status, remove_domain |
Custom domains for apps. |
list_pods, create_pod, exec_in_pod, delete_pod |
HivePods. |
list_databases, create_database, database_connection |
Databases. |
usage_and_cost |
Your plan, usage and estimated bill. |
delete_app |
Delete an app. |
Destructive tools (delete_app, delete_pod) only act when called with confirm: true; otherwise they describe what would be deleted.
Troubleshooting
Section titled “Troubleshooting”- “Not signed in to DockHive”: run
hivepod loginin a terminal, then retry. - The tool doesn’t appear: check the full path to
hivepod, then restart your MCP client. - See what’s happening: set
HIVEPODS_MCP_LOG=INFOin the server’s environment; logs go to stderr.