Access stays inside your boundaries
Choose the organizations, infrastructure and resources your agents may reach. Every request is checked against current permissions.
// AI-native deployment & runtime infrastructure
Your agent decides what to build and how. AgentDeploy coordinates deployment, provisioning, connectivity and operations across infrastructure you choose and control.
Deploy and provision apps and services across your infrastructure—from any supported agent, anywhere.
https://mcp.agent-deploy.ai/mcp
// One neutral control plane
AgentDeploy connects your agents to infrastructure you choose and control. It coordinates deployment, provisioning, connectivity and ongoing operations without selling or operating hosting capacity.
Verified releases, chosen environments, health checks and service entry points.
Gateway, Mesh and Tunnel paths with explicit identity and access policies.
Observed status, logs, stop and resume, version rollback and audit records.
Run in your cloud accounts, provider runtimes, edge sites or private data centers.
AWS / GCP / Azure / Cloudflare / Edge / On-premKeep identity, internal APIs, CI/CD and observability in your operating model.
Explore enterprise deployment ↗The Edge Runtime and customer-side clients will be open sourced so teams can inspect behavior, trust boundaries and updates.
Edge Runtime / clients / adapters// How it works
Add the hosted MCP endpoint and sign in. You choose which organizations the agent may touch; access is checked again on every request.
The agent builds with its own tools in your workspace. AgentDeploy never needs your repository or a shell on your machine.
The built artifact is uploaded and verified as an immutable release. Your agent can inspect its status at every step.
Validate on a separate preview, then promote that exact release. Production always requires your explicit confirmation.
// Autonomous within your boundaries
✓ ready preview-r7.site.exampleProduction stays on r-6 while you review r-7.
✓ ready www.site.exampleThe same immutable release moves to production. No rebuild.
✓ ready www.site.exampleCode rolls back. Your stored application data stays in place.
Choose the organizations, infrastructure and resources your agents may reach. Every request is checked against current permissions.
Use scoped network tickets and temporary policies so access can end when work completes or the grant expires.
Agents can prepare and verify a release. Promotion to production still requires your approval and respects the latest observed state.
// Runtimes
HTML or any built frontend, published as a verified artifact to a compatible target you control.
dist/
├── index.html
├── styles.css
└── assets/
Websites · landing pages · frontends
TypeScript fetch handlers and bound resources, deployed to compatible customer-controlled or third-party runtimes.
export default {
async fetch(request, env) {
return new Response("live");
}
}
APIs · webhooks · data-backed apps
Pinned Linux OCI images serving HTTP, placed on eligible nodes in your cloud, edge or private infrastructure.
image app@sha256:…
port 8080
health /health
runtime linux / oci
Existing services · custom stacks
// Connect
Copy this prompt into your agent. It will follow the official guide to help configure MCP and walk you through sign-in.
Help me connect this agent client to AgentDeploy. Read https://install.agent-deploy.ai/agent first, identify my client and operating system, and check its existing MCP configuration. Add https://mcp.agent-deploy.ai/mcp using the supported setup for this client, preserving other servers. Install the official publishing Skill if supported. Guide me through browser sign-in and organization authorization. Then verify the MCP connection and report the organizations I can access. If you cannot change the configuration directly, give me the exact steps for this client.
# add the server, then run /mcp to sign in
claude mcp add --transport http --scope user agentdeploy https://mcp.agent-deploy.ai/mcp
# install the publishing Skill
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client claude
codex mcp add agentdeploy --url https://mcp.agent-deploy.ai/mcp
codex mcp login agentdeploy
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client codex
opencode mcp add agentdeploy --global --url https://mcp.agent-deploy.ai/mcp
opencode mcp auth agentdeploy
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client opencode
# ~/.cursor/mcp.json
{
"mcpServers": {
"agentdeploy": { "url": "https://mcp.agent-deploy.ai/mcp" }
}
}
Gemini CLI, GitHub Copilot, VS Code, ChatGPT, stdio and more →
Then try“Publish this project to AgentDeploy as a preview and send me the link.”
// Enterprise deployment
Business and engineering teams use approved agents to build applications. Platform teams bring existing cloud, edge and private infrastructure under one control plane and define where workloads may run.
Define allowed nodes, environments, network paths and user access before teams deploy.
Publish a controlled service entry and provide an authorized Gateway path to the internal APIs it needs.
Inspect deployment, runtime and entry status. Associate versions and actions with the responsible identities.
One internal application, one test environment, one Gateway, one internal API and one user group. Verify deployment, authorized access and a complete rollback.
OAuth, open APIs and runtime metrics are available. Enterprise SSO/SCIM, approval workflows and external system adapters are scoped to the integration project.
// A few useful answers
Keep your existing editor and build tools. Your agent builds locally, then uses AgentDeploy MCP tools to package and publish the output.
Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode and other clients with remote MCP support. The agent guide has the current setup options.
In infrastructure you choose and control: your cloud accounts, third-party runtime providers, edge sites or private data centers. AgentDeploy coordinates eligible targets through the control plane.
The recommended flow is a separate preview followed by explicit approval to promote that exact release. Your agent can then inspect status, read logs and roll back supported deployments.
Your teams and infrastructure providers keep responsibility for capacity, application quality and data permissions. AgentDeploy unifies delivery, connectivity and agent automation with APIs for your existing systems.
No. AgentDeploy is a neutral third-party control plane and does not sell or operate hosting capacity. The customer-side Edge Runtime and clients will be open sourced for transparency.
Connect an agent, unify the infrastructure you already choose and automate operations within boundaries you control.
> built for agents. ready to deploy.