Supported clients
Claude Desktop and Claude Code are the only clients named in current RenderDraw workflow documentation.
Integration discovery
RenderDraw MCP
RenderDraw documents an MCP server for AI agents that need to trigger RenderDraw workflow runs from conversation context. The documented audience is teams using Claude Desktop or Claude Code to start workflows without building a custom API integration.
What is verified in this repository
Workflow-run triggering
The documented MCP capability is exposing workflow run triggers as MCP tools, so an AI agent can trigger a workflow directly from conversation context.
Workflow context
Related workflow documentation says knowledgebase context can be configured in workflow definition JSON for teams using the Workflow API or MCP server to build automated pipelines.
Best-fit uses and limitations
Best fit
Teams using Claude Desktop or Claude Code that want an AI agent to trigger a RenderDraw workflow run from conversation context. Workflow design, data handling, and review behavior must be confirmed for the specific deployment; they are not MCP behavior established by this repository.
Representative task
Trigger a RenderDraw workflow run from a conversation.
Limitations
This page does not establish a complete MCP tool catalog, data-access scope, or production connection method. Do not treat the documented trigger capability as evidence of additional read or write tools.
Connection, controls, and support
Published-information boundary
Connection configuration, endpoint, transport, client-specific installation steps, authentication method, tenant-isolation mechanism, permission scopes, versioning, and support process are not published in this repository.
Tool counts and toolset counts are not published because they are not verifiable from this repository.
| Topic | Published status | Safe interpretation |
|---|---|---|
| Authentication | Not published for MCP | Do not reuse workflow API examples as MCP connection instructions. |
| Tenant isolation and permissions | Not published for MCP | Confirm tenant and scope behavior with RenderDraw before any production access. |
| Read/write boundaries | Only workflow-run triggering is documented | Do not assume other tools, data reads, writes, or administrative operations. |
| Approval and safety behavior | No MCP-specific behavior is published | Workflow documentation describes human review gates generally; confirm whether and how a specific MCP-triggered workflow applies them. |
| Versioning, troubleshooting, and support | Not published for MCP | Contact RenderDraw for current deployment guidance and support routing. |
Related resources
- About RenderDraw for platform context, workflow areas, and evaluation guidance.
- Workflow triggers for the source documentation that names the MCP integration.
- AI context configuration for related workflow-definition context.
- Workflow library for use cases and workflow design resources.
Frequently asked questions
Which clients are documented?
Claude Desktop and Claude Code. The repository does not publish support for other MCP clients.
Can I use this page to configure a connection?
No. Endpoint, transport, installation, and authentication details are unavailable here. Contact RenderDraw before configuring a production connection.
Does MCP bypass review controls?
No MCP-specific approval behavior is documented. Confirm the workflow’s review and approval behavior before using it for commercial, compliance, or submission decisions.