JetDeploy JetDeploy
Cloud platform for web apps and databases

Deploy your app.
Just ask.

JetDeploy hosts your web apps and databases: push your code and get builds, HTTPS, logs and zero-downtime deploys, with no servers to run. Connect the agent you already use, from Claude to Cursor, and it does the whole setup from one prompt.

Get started Connect your agent
Claude Claude Code ChatGPT Codex Copilot Cursor

Claude and Claude Code are trademarks of Anthropic, PBC. ChatGPT and Codex are trademarks of OpenAI. GitHub Copilot is a trademark of GitHub, Inc. Cursor is a trademark of Anysphere, Inc. JetDeploy is an independent product, not affiliated with or endorsed by any of them.

jetdeploy · mcp
Put this app in production on JetDeploy with a Postgres.
On it. Creating your stack.
create_app my-app main
create_service postgresql ready
set_envs DATABASE_URL wired
create_pod web :8000 public
git push build & deploy 2m 04s
get_operation deploy SUCCESS
https://my-app.jetdeployapp.com
Want a custom domain or a Redis? Just ask.
One prompt is all it takes to put your app online.
Python
Node.js
PHP
Go
Ruby
Java
Rust
Erlang
Any Dockerfile
PostgreSQL
MariaDB
Redis
OpenSearch
RabbitMQ
Python
Node.js
PHP
Go
Ruby
Java
Rust
Erlang
Any Dockerfile
PostgreSQL
MariaDB
Redis
OpenSearch
RabbitMQ
Connect

Connect in 30 seconds.

Paste one URL. Sign in with JetDeploy. Allow. That's it: OAuth, no tokens to copy around.

Claude

In claude.ai: Settings › Connectors › Add custom connector, paste the URL.

https://jetdeploy.com/mcp

Claude Code

Run it, then /mcp to sign in.

claude mcp add --transport http jetdeploy https://jetdeploy.com/mcp

GitHub Copilot

In VS Code: MCP: Add Server, or this entry in .vscode/mcp.json. The login opens on first use.

Install in VS Code 
{"servers": {"jetdeploy": {"type": "http", "url": "https://jetdeploy.com/mcp"}}}

ChatGPT

Settings › Plugins › Developer mode, then chatgpt.com/plugins › +, Server URL with OAuth, Create.

https://jetdeploy.com/mcp

Codex

Run it: Codex opens the JetDeploy login for you.

codex mcp add jetdeploy --url https://jetdeploy.com/mcp

Cursor

Add this entry to .cursor/mcp.json. Cursor asks you to sign in.

Add to Cursor 
{"mcpServers": {"jetdeploy": {"url": "https://jetdeploy.com/mcp"}}}
Any MCP client with OAuth works the same way
How it works

From prompt to production.

1

Connect

Add the MCP server to your agent.

2

Ask

Say what you want in production.

3

Push

Your agent pushes the code. The push triggers the deploy.

4

Live

Online at an HTTPS URL. Read logs, run commands, add your domain from the chat.

What you get

One prompt. Everything provisioned.

Every tool your agent needs, with the same permissions and the same guardrails as the console.

Databases on demand

Ready in about a minute. Your agent reads the credentials and wires them into the app's environment, nothing to copy.

PostgreSQL MariaDB Redis OpenSearch RabbitMQ

Zero-downtime deploys

The new version takes traffic only once it's ready. A build or pre-deploy that fails leaves the running version serving.

Migrations, handled

A pre-deploy script runs after the build and before traffic. Your agent sets it for you.

Logs and commands, from the chat

Read runtime logs and build output, run one-off commands. All of it is a tool.

Your domain, HTTPS included

You add the DNS record it gives you; the agent validates and attaches the domain. The certificate arrives on its own.

Push

The push is the deploy.

The one thing an agent can't do from a chat window is push your code. An agent with a terminal, such as Claude Code, Codex, Copilot or Cursor, pushes by itself. Claude and ChatGPT hand you the command.

Every push to your branch builds and rolls out the new version. Nothing else to trigger.

git remote add jetdeploy https://git:<token>@jetdeploy.com/git/<app>
git push jetdeploy main

<token> is your Git Access Token, on the App page and under Integrations › Git Access Token. 

name: Deploy to JetDeploy
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - run: |
          git -c credential.helper= -c credential.helper='!f() { echo username=git; echo "password=$JD_GIT_TOKEN"; }; f' \
            push https://jetdeploy.com/git/<app> HEAD:refs/heads/main
        env:
          JD_GIT_TOKEN: ${{ secrets.JD_GIT_TOKEN }}

Add the Git Access Token as the JD_GIT_TOKEN secret of the repository. fetch-depth: 0 is required: a push from a shallow clone is refused.

FAQ

Questions, answered.

Anything else? hello@jetdeploy.com

Yes. Create it, then connect the agent: the connection is authorized on the account you sign in with and works on every organization you belong to.

Only what it was granted, and you see the grant before you allow it. With read alone it changes nothing. With write it can deploy, restart, stop and destroy, exactly like you from the console, and you can revoke it at any moment.

One fixed price per organization for a reserved amount of vCPU and memory, shared by every app and service you run. No per-process sizing, no surprises. See Billing in the docs.

No. Everything the agent does you can do yourself: create the app in the console, push with git, add a database from the catalog. The agent is the fast lane, not the only lane.

Yes. Everything is also a JSON API with a public OpenAPI schema, and llms.txt describes every step the way an agent needs it.
Your agent is waiting

Ready when you are.

Copy the prompt, connect the agent, watch it ship.

Put this app in production on JetDeploy with a Postgres.
Get started Connect your agent
Read the docs llms.txt for your agent Talk to us