Advanced

Deployments

Deployments let you promote agents, actions, and MCP servers from one environment to another — for example, from Development to Production — without manual recreation.

What is Deployment?

A deployment copies the configuration of an agent, action, or MCP server from a source environment into a target environment. Meebly automatically detects whether a matching resource already exists in the target and lets you choose to overwrite it or create a new one.

Deployments are always initiated from the source resource using the Deploy button on its detail page or in the environment's resource list.

Actions & MCP Servers

Deploying an action or MCP server follows the same flow:

  1. Open the action or MCP server you want to deploy and click Deploy.
  2. Select the target environment from the dropdown. Meebly immediately checks whether a resource with the same identifier already exists there.
  3. If a conflict is detected, you'll see a warning. Choose to Overwrite the existing resource or cancel and deploy as a new one under a different name.
  4. Click Deploy to confirm.
Actions are matched by Operation Name. MCP servers are matched by Name + Type. Two resources are considered a conflict only when both identifiers match.

Conflict Detection

Before deploying, Meebly compares the source resource against everything in the target environment using the following rules:

ResourceMatch Criteria
ActionSame Operation Name
MCP ServerSame Name and Type
AgentSame Name

A resource with no match in the target environment is marked New and will be created automatically. A resource that matches an existing one is marked Conflict and requires a decision before deploying.

Agents

Agent deployment is a two-step process that handles the agent itself along with all of its associated tools, MCP servers, and sub-agents in a single operation.

Review Tree

After selecting a target environment, you'll see a full review tree showing every resource that will be affected:

  • Main agent — always deployed; shows whether it will be created new or overwrite an existing agent with the same name.
  • Shared tools / MCP servers — tools used by two or more sub-agents are hoisted to a shared section and deployed once.
  • Sub-agent tools — tools and MCP servers belonging to individual sub-agents appear under each sub-agent's row.

Each conflicting resource shows an Overwrite checkbox. Unchecking it marks the item as Don't Overwrite — the resource in the target environment is left unchanged, but the agent will still be linked to its existing counterpart there.

Setting a sub-agent to Don't Overwrite automatically applies the same to all of its owned tools and MCP servers, since updating their configuration without updating the agent itself would have no effect.

A summary line at the bottom of the review panel shows the total counts of overwrites, non-overwrites, and new resources before you confirm.

Orchestration Agents

Orchestration agents coordinate other agents as sub-agents rather than calling actions directly. The review tree adapts accordingly:

  • Orchestration agents show the Sub-agents section. Each sub-agent is expandable to reveal its own tools and MCP servers.
  • Assistant agents show only This agent's tools and MCP servers — no sub-agents section.

Sub-agents are matched to counterparts in the target environment by name. If no match exists, a new sub-agent will be created as part of the deployment.

RAG Files

If the source agent has a knowledge base (RAG), Meebly automatically copies all uploaded files to the target agent and re-embeds them in the target agent's vector store. No manual upload is required.

The target agent's existing knowledge base is always replaced by the source agent's files — including any documents that were uploaded directly to the target agent.
Deploying an agent that has RAG disabled onto a target agent that previously had RAG enabled will delete the target agent's existing knowledge base entirely.
Last updated: March 2026Report an issue