---
topic: connectors
needs_human: The person adds the connector in their AI tool and signs in to Embarko.
---

[← Guide home](https://embarko.ai/docs)

# Connect Embarko to an AI tool

**On this page:** Available for, Its tools, Steps, Limits, What to tell the person

> Plain words unless the person is a developer. Never invent a link, name or code. [Rules](https://embarko.ai/docs/prerequisites)

A connector/plugin lets an AI tool deploy and manage the person's apps from inside the chat, signed in as them. No token, nothing to install, and it works where a sandbox blocks ship.embarko.ai. Only the person can add it.

**Done when:** The Embarko tools (deploy_app, read_app, update_app, app_danger_zone) are in your tools, or you told the person the one link to add them.

**Available for**

| AI tool | Add it |
| --- | --- |
| Claude | https://claude.ai/directory/embarko |
| ChatGPT (plugin) | https://chatgpt.com/plugins/embarko |

**Its tools**

- `deploy_app`: Deploy or update an app from its files: { appName, files, appType?, version? }. Send the whole app every time. Use this for apps under 150 KB total. One call, all files. The app goes straight into the person's account: permanent, nothing to claim.
- `start_upload`: Only for apps over 150 KB total or long conversations: { appName, files } with the first part. Returns uploadId. Apps under 150 KB must use deploy_app in one call. Upload expires after 60 minutes unused.
- `add_upload_files`: The next part, with uploadId: { files }. "append": true on a file continues one already sent, so one big file can be split.
- `deploy_upload`: Deploy what the upload holds: { appName, uploadId }. Same reply as deploy_app.
- `read_app`: action: "status", "logs", "deployments", "env_vars", "domains" or "analytics", with appName. A rename's progress is not a read_app action: read the rename reply's links.status.
- `update_app`: action: "set_env_vars", "apply_env_vars", "register_domain", "verify_domain", "rollback" or "submit_feedback", with appName.
- `app_danger_zone`: action: "delete_env_var", "delete_domain", "rename_app" or "delete_app", after the person confirms.

**Steps**

1. Look at your tools. If deploy_app is there, the connector is already added: use it and stop here.
2. Find the person's AI tool in available_for. In ChatGPT, say "plugin", not "connector": that is ChatGPT's word for it. Give them that link in one line: "Connect Embarko here once, and I can deploy for you directly from now on."
3. They open it, add Embarko, and sign in. It is the same sign-in as embarko.ai, so they see the apps and workspaces they already have.
4. Their tool not listed (Gemini, and every tool other than Claude and ChatGPT today)? There is no connector for it yet. If you can reach ship.embarko.ai, deploy over HTTP (see quickstart). If you cannot, give them the app as a .zip for the upload page (see prerequisites, route 4).

**Limits**

- You cannot add a connector yourself; only the person can.
- deploy_app carries every file's full text in one call, so your reply size is the limit, not Embarko. Under 150 KB in total: call deploy_app once with all the files. Do not use start_upload for small apps. Over 150 KB in total, or a long conversation: send it in parts with start_upload, add_upload_files and deploy_upload. Finish and call deploy_upload within 60 minutes, from the same token, or the upload expires (see large_apps on the deploy topic).
- Do not hold up a deploy waiting for it: if HTTP works, deploy now and mention the connector once.
- Each topic's connector steps give the arguments. Your tool definitions have the exact shape.
- No schedule or Showcase actions yet: schedules deploy through embarko.json in deploy_app; running one now and Showcase listing need the person (see schedules, showcase).
- No alert actions yet: where alerts go, tests, muting and past outages need HTTP with a deploy token, or the person in the app's Settings → Alerts (see alerts).

**What to tell the person**

- connect: "Connect Embarko to {your AI tool} once ({link}), then ask me again. After that I can deploy for you directly."

**Next:** Connector in your tools: deploy with deploy_app. Otherwise give the person the link, and carry on with the route that works today.

**Related:** [prerequisites](https://embarko.ai/docs/prerequisites) · [quickstart](https://embarko.ai/docs/quickstart)

---

[Guide home](https://embarko.ai/docs) · JSON: add .json