Model Context Protocol (MCP)

MCP connects your AI to JustDeploy so you can deploy and manage your apps without copying a guide each time.

What you'll need

A JustDeploy account and Codex or Claude Code running on your computer. A browser chat cannot change your local MCP settings. MCP is optional; the Quickstart copy-paste deployment flow still works without it.

Copy MCP setup

Open MCP in the sidebar, above your account menu. If you have no organization yet, use Connect your AI with MCP on the organization creation screen to open the same page.
Click Copy MCP setup. This creates a connection valid for 90 days, covering all organizations your account can access.
Paste it directly into Codex or Claude Code. Your AI checks the token, saves its user-level settings and verifies the connection. No extra JustDeploy login, key entry or CLI installation is needed.

The copied setup contains a secret with your account’s access. It will be present in that AI conversation and your private client settings. Do not save it in your project, deployment environment or a shared document. Disconnect it on the MCP page if it is exposed.

Copying again creates another connection without revoking older ones. If copying fails, stay on the page and use Copy same MCP setup. The original secret cannot be retrieved after you leave. Connections show a prefix, creation time and expiration so you can identify and disconnect unwanted ones.

Verify the connection

Settings saved is not the same as connected. Your client may ask for security approval or a restart. After it loads the configuration, ask your AI to run list_organizations through MCP. A successful empty list also confirms the connection; do not create an organization just to test it.

A direct HTTP check verifies the token only. Do not report the connection as complete until an actual MCP tool succeeds in your client. Keep the client’s security approvals enabled.

Other MCP clients

Clients that cannot edit local settings use the existing OAuth connection. Add this server URL using your client’s native remote MCP support, sign in to JustDeploy and approve the connection. Existing OAuth connections continue to work.

https://mcp.justdeploy.ai/mcp

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. Clients that support registry discovery can find the same remote server under this name:

ai.justdeploy/mcp

Trouble connecting?

Setup token rejected or expired: copy a new MCP setup from Console. Do not switch to OAuth to repair a direct-token setup. Its 90-day expiration does not extend when used.
Verification unavailable: keep the existing connection. Follow the response’s retry delay and do not create replacement tokens for a temporary network problem.
Configuration conflict or write denied: keep other servers and security settings intact. Follow your AI’s explanation instead of weakening client permissions.
OAuth sign-in finished but tools are missing: reload the client and verify list_organizations. A browser success page confirms only sign-in, not the MCP connection.

What you can do

Ask your AI to deploy apps, check logs, work with databases and files, or manage project settings, environment variables and app keys. Your AI follows your account’s permissions.

Environment values and newly issued app keys may remain in your AI’s history. Use Console or private local settings if you do not want to share a secret with your AI.