Connect your AI

Use Deploy Hatch with any compatible MCP client

Deploy Hatch is vendor-neutral. Any MCP client that supports the required remote HTTP transport and bearer authentication can use the same machine contract.

Connection

Configure the credential through the client's secure authentication or secret mechanism. Do not hardcode it into a repository.

MCP endpoint:
https://deployhatch.com/api/mcp

Authentication:
Authorization: Bearer <project-scoped-agent-credential>

Client requirements

Connect to a remote HTTP MCP endpoint.
Send an Authorization bearer header.
Discover the MCP tool catalog.
Call tools using their declared JSON schemas.
Preserve tool results such as immutable revision and deployment IDs rather than inventing identifiers.

Bootstrap sequence

The live capabilities and MCP tool catalog are authoritative. Integrations should discover them rather than pinning themselves to a permanently frozen list.

Capabilities
  ↓
Credential/project context
  ↓
Workload inspection
  ↓
Trusted project configuration/state
  ↓
Deployment
  ↓
Diagnostics
  ↓
Authorized recovery
  ↓
running + healthy
  ↓
Public URL

Representative tools

deployhatch_get_capabilities
deployhatch_get_context
deployhatch_inspect_workload
deployhatch_get_project_state
deployhatch_get_configuration
deployhatch_update_configuration
deployhatch_deploy
deployhatch_diagnose
deployhatch_source_recover
deployhatch_configuration_recover
deployhatch_platform_recover

This list is illustrative of the current integration. Always treat the live MCP tool catalog and Deploy Hatch capabilities contract as authoritative.

Project self-discovery

A project-scoped credential binds the client to its authorized Deploy Hatch project. The agent can query credential context to discover the project instead of requiring the human to copy internal IDs into chat.

Safe recovery

Diagnostics expose failure stage, category, diagnostic code, failure owner, agent/human action requirements, next action, and recovery disposition. The client should perform only the action authorized by that result and must stop when human input is required.

Compatibility

Deploy Hatch can work with MCP clients that support the remote HTTP transport and authentication requirements described here. MCP support varies by client, so verify that your client can send the required bearer header before relying on it.

Keep going

Agent API

Read the public machine-contract details.

Agent recovery

Understand bounded recovery semantics.