Remote MCP
Connect Claude Code, Codex, Cursor or ChatGPT to Homemade over MCP.
Homemade runs an MCP server at https://api.homemade.dev/mcp. It has one tool for every public API operation, so an agent can create VMs, run commands in them, read the results and work with projects.
Connect with OAuth
claude mcp add --transport http homemade https://api.homemade.dev/mcpStart Claude Code and run /mcp to connect. Your browser opens, you sign in to Homemade and approve the app on the consent page. The app then acts as you.
Use an API key
Use a key when there is no browser: CI, servers and scripts. Create one on the API keys page in your account settings, or run homemade api-key create --name ci.
claude mcp add --transport http homemade https://api.homemade.dev/mcp --header "Authorization: Bearer $HOMEMADE_API_KEY"Cursor
Add this to ~/.cursor/mcp.json:
{ "mcpServers": { "homemade": { "url": "https://api.homemade.dev/mcp" } } }Cursor opens the sign-in when you enable the server. To use a key instead, add "headers": { "Authorization": "Bearer <your key>" } next to url.
Codex
codex mcp add homemade --url https://api.homemade.dev/mcpOr add it to ~/.codex/config.toml:
[mcp_servers.homemade]
url = "https://api.homemade.dev/mcp"ChatGPT
In developer mode, add a custom connector under Settings, Connectors. Use the URL https://api.homemade.dev/mcp and choose OAuth.
Other clients
Use the server URL https://api.homemade.dev/mcp with the Streamable HTTP transport. Sign in with OAuth, or send Authorization: Bearer <API key>.
Disconnect an app
Apps you approved with OAuth are listed under Connected apps on the API keys page in your account settings. Disconnect one and it loses access at once. An app connected with OAuth can't create API keys.
API keys keep working on the REST API too. See Authentication and errors.