Model Context Protocol (MCP)

MCP connects your AI directly to JustDeploy, so you do not need to copy and paste a guide each time. Once connected, your AI can create projects, put apps online, read logs, query databases, and handle other common JustDeploy tasks from the chat you already use.

What you'll need

An AI tool that supports MCP. See the list below.
A JustDeploy account. Don't have one yet? You'll create it free when you connect, with no API keys to set up.

MCP server URL

Add this URL to your AI tool:

https://mcp.justdeploy.ai

When you add it, your browser opens a JustDeploy sign-in. Sign in with Google or email and approve the connection, with no keys to paste. One connection covers all your organizations; your AI asks which one to use when you deploy. In Account settings you can see when and from which IP each connection was last used, or disconnect it immediately.

Opening this address directly in a browser can show “Method Not Allowed” (405). That is expected: this is an MCP server address, not a web page. Add it to your AI tool instead.

In the MCP Registry

JustDeploy is published in the official MCP Registry, so AI clients and connector directories that read it can add JustDeploy without pasting a URL. Look for:

ai.justdeploy/mcp

Search for it in your client's connector directory, or find it at registry.modelcontextprotocol.io. If your client doesn't support registry discovery yet, just use the server URL above. Both connect to the same place.

Client setup

The simplest way to set this up is to ask your AI to do it. It can run the commands and edit its own settings, so you do not have to open a terminal or find a config file. Paste one of these and let it work.

Signing in still happens in your browser, and that part is yours: a JustDeploy page opens, you sign in, and you approve the connection. Your AI cannot do that step for you.

Setting it up yourself

If you would rather do it by hand, here is what each tool needs. Modern clients connect natively over remote MCP: register the one URL above and they handle the OAuth sign-in for you, with no keys and no manual client ID.

MCP is optional. To skip all of this, use the copy-paste flow in Quickstart. It needs no setup and works the same way.

Codex

Add this to ~/.codex/config.toml. Codex opens a browser to sign in the first time it starts the server.

~/.codex/config.toml

[mcp_servers.justdeploy]
url = "https://mcp.justdeploy.ai"
auth = "oauth"
startup_timeout_sec = 120.0

Claude Code

Add the server from your terminal, then run /mcp inside Claude Code and pick JustDeploy to sign in. Add -s user to make it available in every project.

Terminal

claude mcp add --transport http justdeploy https://mcp.justdeploy.ai

Antigravity

Add this to ~/.gemini/config/mcp_config.json for all projects, or .agents/mcp_config.json for one workspace. Return to Settings → Customizations and refresh the MCP server list, then authenticate JustDeploy.

~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "justdeploy": {
      "serverUrl": "https://mcp.justdeploy.ai"
    }
  }
}

Claude Desktop

Open Settings → Connectors, click "Add custom connector," paste the server URL above, and click Add. A browser window opens for you to sign in.

Official docs per tool

Using a tool not listed above, or want the full options? Open your tool's official MCP docs:

Verify the connection

Signing in is not the same as being connected. Confirm it actually worked:

Your client shows JustDeploy as connected and lists its tools.
Ask your AI to run list_organizations. If it returns your organizations, you are connected.

Seeing "Authorization successful" in your browser is not the same as being connected. That message only means the sign-in step finished, and it is shown by your client, not by JustDeploy. The real check is whether your client loaded the tools and list_organizations responds.

Trouble connecting?

If the sign-in page keeps reopening, with your client asking you to connect again and again, the client could not store its token. Set it up with the native remote MCP + OAuth method for your tool shown above.

Some older clients connect through a proxy (npx -y mcp-remote …) instead of native remote MCP. Avoid the proxy if your client supports native remote MCP: it can fail to save the OAuth token and leave you stuck in a sign-in loop. Use the native method above.

What you can do

JustDeploy MCP gives your AI tools for common tasks across all your organizations:

Organizations: list your organizations and choose where to deploy
Projects: create, view, deploy, check status
Builds: trigger deploys, view build status
Schedulers: set when a scheduled project runs, pause or resume it, run it now
Environment variables: set, list, delete
Firewall: add or remove IP rules
Database: list tables, run queries
Storage: list, download, delete files
App keys: issue the key your app needs to reach its own database and storage, list them, revoke them
Logs: read your app logs