MCP editor for agents
MCP editor for agents
Use a dedicated MCP transport so AI agents can read published vs workspace drafts, edit draft tools, and optionally save or publish versions.
Overview
Rapid MCP exposes an editor MCP endpoint alongside your normal server stream. Agents connect with the same authentication as production, but get a small, purpose-built tool surface to:
- Compare the published snapshot with the workspace (draft) snapshot
- Create or update tools on the workspace draft
- Save an immutable version from the current draft, and publish a saved version by id (same semantics as the dashboard versions flow)
When an agent changes a tool, saves a version, or publishes, the dashboard can refresh automatically: the backend notifies connected browsers over the same Socket.IO channel used elsewhere, so the manage-server UI stays in sync with edits made from Cursor or other MCP clients.
Video walkthrough
Why it exists
- Published vs draft: Production traffic should keep using immutable published versions. Agents need to see what’s live and what you’re still editing.
- Scoped writes: The editor transport is intentionally small: draft tool upserts plus explicit
saveVersion/publishVersiontools. UsepublishVersiononly when you intend to change what production considers published. - Operator UX: Editors working in the web UI see updates when an agent changes the draft, without manual refresh.
Editor tools
The editor MCP registers:
| Tool | Purpose |
|---|---|
getPublishedMCPServer | Published snapshot metadata and tools (optional version query supported by your deployment). |
getPublishedVersion | Alias of getPublishedMCPServer for older clients. |
getWorkspaceMCPServer | Current workspace (draft) snapshot metadata and tools. |
upsertTool | Create or update a tool on the draft. Does not publish. |
saveVersion | Snapshot the current draft into a saved version. Optional input: comment (string, max 500). Returns versionId. |
publishVersion | Publish an existing saved version. Input: versionId. |
Saving and publishing use the same server-side rules as the product (project membership, version records, published pointer). Treat publishVersion as a production-affecting action.
For background on publishable versions, see Environments & versions.
Endpoint
Use the editor stream URL configured in your MCP client (same host and auth as your main MCP server, with the editor path your deployment exposes—typically the stream/edit route on the MCP backend).
Configure it like any other MCP server entry (URL + Authorization headers, etc.). Your JWT and server id must allow access, consistent with Authentication.
Dashboard sync
After a successful draft tool upsert, version save, or publish from the editor MCP, Rapid MCP emits a SERVER_CHANGED-style event to the server room so open manage server tabs refetch. Tool edits use payload { type: "tool" }; version save/publish use { type: "version", data: { versionId } }.
Related
- Environments & versions — published snapshots vs workspace
- MCP tools — tool schema and behavior
- Connect to agents — URL, headers, and clients