Model Context Protocol (MCP)

Let your AI talk to JustDeploy directly. No more copying guides into chat — once you add JustDeploy as an MCP server, your AI can deploy your app, read logs, query databases, and manage everything right from where you already chat with it.

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 — no API keys to set up.

MCP server URL

Add this URL to your AI tool:

https://mcp.justdeploy.net

When you add it, your browser opens a JustDeploy sign-in. Sign in with Google or email and approve the connection — no keys to paste. One connection covers all your organizations; your AI asks which one to use when you deploy. You can disconnect it anytime from your account settings.

Client setup

Modern AI clients connect natively over remote MCP — register the one URL above and they handle the OAuth sign-in for you (no keys, no manual client ID). Set up yours below.

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.net

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.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project). Cursor opens a browser to sign in the first time your AI uses it.

~/.cursor/mcp.json

{
  "mcpServers": {
    "justdeploy": {
      "url": "https://mcp.justdeploy.net"
    }
  }
}

VS Code

Add this to .vscode/mcp.json in your workspace (or run "MCP: Open User Configuration" for all workspaces). VS Code opens a browser to sign in.

.vscode/mcp.json

{
  "servers": {
    "justdeploy": {
      "type": "http",
      "url": "https://mcp.justdeploy.net"
    }
  }
}

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.net"
auth = "oauth"
startup_timeout_sec = 120.0

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 — your client asks 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 a full set of tools 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
Environment variables — set, list, delete
Firewall — add or remove IP rules
Databases — list tables, run queries
Storage — list, download, delete files
Logs — read your app logs