MCP connection guide

Connect any MCP-compatible agent to RenderMark

Choose remote MCP for the simplest cloud connection. Choose local MCP when the agent must write files or use local browser and credential flows.

Recommended

Hosted remote MCP

In any client that supports MCP over Streamable HTTP, add a server named RenderMark with the endpoint below. Complete OAuth when the client opens the authorization flow. No package or local process is required.

https://mcp.rendermark.app/mcp

Hosted MCP can render and validate Markdown, publish previews and persistent links, and manage or sync authenticated RenderMark documents. It cannot save files to the agent's local filesystem.

Local stdio MCP

Add the following server to any stdio-compatible MCP client. The client runs the npm package as a local process, so the tools can save PDF, DOCX, and HTML files, batch export, render images and visual diffs, and publish to Google Docs.

{
  "mcpServers": {
    "rendermark": {
      "command": "npx",
      "args": ["-y", "@rendermark/mcp-server@latest"]
    }
  }
}

Publishing workflows require OAuth or a RenderMark API key from API key settings. Keep keys in environment variables or your client's secret storage.

Agent Skill

The RenderMark Agent Skill is an optional folder of instructions for skill-compatible agents. It helps the agent recognize RenderMark tasks and choose the right MCP tool, but it does not create the MCP connection itself. Skill installation differs by provider.

View provider-specific setup on GitHub

Verify the endpoint

Opening the endpoint without credentials should return 401 Unauthorized with OAuth metadata. That response means the server is live and waiting for authentication.