Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
// DEVELOPMENT
Develop, preview, promote
Build locally, validate on a separate Preview, then promote the tested immutable Release with explicit production authorization.
Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client codex
claude mcp add --transport http --scope user agentdeploy https://mcp.agent-deploy.ai/mcp
02 / Authorize AgentDeploy
/mcp
03 / Install the publishing Skill
Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client claude
Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client opencode
Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client qoder
Connectors → AgentDeploy → Connect → authorize in browser
03 / Install the publishing Skill
Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client bundle
# Include the installed brand Skill directory in this brand's connector.
# Keep auth_mode unset to use the standard MCP OAuth flow.
In the Doubao Work desktop client (豆包工作), open Plugins · Skills · Partners → Plugins → + Add → New custom plugin. Name it AgentDeploy, select HTTP and OAuth authentication, and paste the server URL below.
https://mcp.agent-deploy.ai/mcp
02 / Authorize AgentDeploy
Save the plugin and connect. Sign in on the AgentDeploy page opened in your browser, select one or more organizations to authorize, and return to Doubao Work when authorization completes.
03 / Verify the connection
Save the plugin, start a new work task, and select AgentDeploy using @ or the Plugins menu. Send the prompt below to check access and inspect deployment candidates before choosing a node.
Use AgentDeploy to list the authorized organizations and deployment nodes that support Static. Show the candidates and ask me to confirm a node before deploying.
Installation uses system tools, without Python or Node. Installed Skill names use the stable brand ID plus -publish, allowing multiple brands to coexist.
curl -fsSL https://install.agent-deploy.ai/skill/publish | sh -s -- --client qwenwork
Both transports use the same immutable artifact, release, deployment, and readiness model.
01Discover
Select an authorized organization and an existing node.
02Build
Produce a static directory, choose a digest-pinned OCI image, or package a Worker module.
03Prepare
Upload or import an immutable content-addressed artifact.
04Deploy
Submit a generation-checked deployment and optional public exposure.
05Observe
Poll status, read bounded logs, stop, start, or roll back.
// Common questions
MCP, Skills, and authorization
Should I use Hosted MCP or stdio?
Use Hosted MCP for the simplest OAuth connection. Use stdio when the agent must package a local build directory or the client cannot complete hosted OAuth.
What does the Agent Skill do?
The Skill teaches the agent the AgentDeploy publishing workflow and tool order. It stores no credentials and does not replace MCP authorization.
Can one authorization cover multiple organizations?
Yes. Select one or more organizations during OAuth consent. AgentDeploy checks the chosen organization and its current permissions again on every request.
Can another MCP client use AgentDeploy?
Usually yes if it supports Streamable HTTP with OAuth 2.1 and PKCE, or local stdio. Use the same MCP endpoint and adapt the configuration shape required by that client.