aidrop.itDocs

Bring an existing repository

Deploy a repository you already have on GitHub: your AI agent links it to aidrop.it, builds it with one call and gives you a live address to open.

Updated

Let your agent build this

Copy one prompt and paste it into Claude Code, Codex or Cursor. Your agent builds what this page describes and puts it online on aidrop.it. Fill in the parts in brackets before you send it.

See the prompt
I have a GitHub repository, [OWNER/REPOSITORY]. Read it first and tell me what it is before you create anything.

Then bring it into aidrop.it as a Service and build it here. Choose the port, health path and size from what the code actually does, and ask me for each secret value it needs before you build. Store each one with project_secret_set under a clear name and list those names in required_secret_names; never print a value back to me or write one into code, the repository, a commit or a log. If the build fails, read the log, fix the cause and build again. When it runs, give me the address; if it cannot run yet, tell me exactly what is missing.

This task comes from the aidrop.it guide "Bring an existing repository": https://docs.aidrop.it/bring-your-repository. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.
On this page

To deploy an existing GitHub repository with your AI agent, install the aidrop.it GitHub App on the account that owns it, then tell your agent to bring it in. The agent reads the code, builds it with one service_build call and gives you a public HTTPS address. Nothing is copied into your repository.

If you have no code yet, the quickstart is the shorter road. If the product needs several parts, such as a frontend, an API and a database, follow the checklist to build and deploy a full app with an AI agent.

The whole page, said once. Replace the repository name with yours before you send it.

Say this to your agent
I have a GitHub repository, acme/support-portal. Bring it into aidrop.it as a Service, build it here, and tell me what is missing if it does not run.

Coming from an AI app builder? These walk-throughs cover what moves and what stays: host a Lovable app, move an app from Base44 or Replit, and deploy a Streamlit app at a link that does not go to sleep.

1. Look at the Team’s repositories first

repositories_list returns the Team’s repositories: the ones on its own aidrop.it Git service and the GitHub ones the aidrop.it GitHub App can reach, each with the Services it already backs. If a repository already backs a Service, you continue in that Service instead of starting a parallel one by accident.

It is not a refusal. One repository may back several Services, and sometimes it must. A Service runs one container on one port, so a monorepo (one repository holding several apps) whose API and web app deploy separately is two Services over one repository.

Your agent checks this before creating anything. If the repository already backs a Service in your Team, it offers you that one and asks, rather than quietly creating a second.

2. Name the deployable

There is no create call: service_build makes the Service on its first call, from the Project and a name you give it. Tell your agent to read the repository first and describe what it found, so what gets recorded matches the code.

Say this to your agent
Read the repository and tell me what it is before you create anything.

It shows you what it read from your code and waits for a yes. Nothing is copied into your repository at any point: your code stays yours.

Say this to your agent
Build it on aidrop.it.
service_build(
  service_id: "8b3e…",
  repository_ref: "acme/support-portal",
  container_port: 8000
)

There is no separate connect step: the first service_build names the repository, and it becomes the Service’s for good. aidrop.it does not read your code to decide how it runs. Your agent passes the port the application listens on, a health path if it is not /, and how the image is built. The build is queued, the deploy reserves the address itself, and your agent polls service_get until it reports a running application.

Code that is not on GitHub goes through repository_create instead. It makes an empty repository on your Team’s own Git service and answers a credential your agent pushes with using its own git. The same service_build links it.

4. If it does not run

service_logs says why. Your agent reads it, changes the code, pushes to the tracked branch and builds again. Pass branch to service_build if the code to run is on another branch. The quickstart describes the address and custom domains in what you get after the first deploy.

Next steps