Use RevoEngine from an MCP client
Discover platform context, resources, prompts, and instance-scoped tools through one Streamable HTTP endpoint.
Connect an MCP server to RevoEngine
Synchronize remote tools, bind credentials through Secrets, and apply per-tool safety and approval policy.
RevoEngine as an MCP server
The public MCP endpoint gives a compatible client a governed view of the RevoEngine instance associated with its credential. It is useful when an IDE, automation client, or AI application needs to:- understand RevoEngine platform and low-code semantics before generating a change;
- discover the tools currently available to its authenticated identity;
- search and inspect instance resources without building a dedicated Platform API client;
- perform validated platform actions with structured inputs and outputs;
- load RevoEngine skills, runtime declarations, and change-safety prompts as standard MCP resources.
MCP is a JSON-RPC protocol surface, separate from the REST-style
/api/v1 Platform API. Its methods are documented in this section and discovered through MCP capabilities rather than generated as individual OpenAPI operations.RevoEngine as an MCP client
An MCP server plugin makes approved third-party or private MCP tools available to the RevoEngine Assistant and autonomous Agents. RevoEngine synchronizes the remote manifest, keeps credentials in Secrets, and lets an administrator govern each discovered operation separately. This direction is appropriate when a team wants RevoEngine AI to work with an existing system without copying its API contract into component code.Keep the two directions separate
Request lifecycle
Supported server capabilities
The current public server supports:- tool discovery and calls;
- resources and resource templates;
- reusable prompts;
- JSON-RPC requests, notifications, and batches;
- session-aware Streamable HTTP;
- an optional authenticated SSE listening connection for session continuity.
tools/list instead of hard-coding a catalogue from this documentation.