Connect Claude to Deploy Hatch

1. Add Deploy Hatch to Claude

In Claude, open Customize → Connectors, choose Add custom connector, and add the Deploy Hatch remote MCP endpoint below. Deploy Hatch is publicly reachable and uses OAuth for interactive Claude connections.

https://deployhatch.com/api/mcp

2. Sign in with Deploy Hatch OAuth

Choose Connect and sign in to Deploy Hatch. Review the requested scopes on the Deploy Hatch consent screen and approve only the authority you want Claude to use. Claude does not need a project-scoped bearer credential for this interactive OAuth connection.

3. Verify project discovery

Enable the Deploy Hatch connector in a Claude conversation and ask which Deploy Hatch projects are available. Claude should use Deploy Hatch project discovery instead of asking you to paste a project UUID or bearer token.

What Deploy Hatch projects do you have access to?

4. Give Claude the deployment goal

Claude can discover the project, request a deployment, follow the returned deployment, and report the stable Deploy Hatch project URL after health/readiness succeeds.

Deploy my Deploy Hatch project named DH-ChatGPT-Tetris. Use Deploy Hatch to discover the project and request a deployment. After requesting it, check the deployment status and tell me the deployment ID, current status, and deployment URL. Do not modify the project's configuration or source code.

5. Preserve the authority boundary

• Source failure: Claude may repair repository source when Deploy Hatch diagnostics require source repair, then use a new immutable revision.
• Configuration failure: use configuration recovery only when diagnostics and the granted authority allow it.
• Platform failure: use bounded platform recovery only when Deploy Hatch classifies it as appropriate.
• Human input required: stop and ask the human. Never infer secrets or bypass the stop.
• Deploy Hatch OAuth does not grant Claude SSH, Docker, database-administrator, GitHub repository-creation, or secret-inference authority.

6. Verify before claiming success

Claude should follow the exact deployment returned by Deploy Hatch and should not call the task complete merely because a deployment request was accepted. The live Deploy Hatch contract is authoritative for lifecycle and health semantics.

7. Claude Code and other MCP clients

If you use Claude Code or another MCP client outside Claude's interactive connector flow, use that client's current remote MCP authentication workflow. Prefer OAuth when the client supports it; project-scoped Deploy Hatch credentials remain available for clients that require bearer authentication.