MCP / AI Agents

Rynko exposes two MCP servers so AI agents can interact with both products through natural conversation.

Server	Product	Purpose	URL
Rynko Render	Document Generation	Create templates, generate PDFs and Excel files	https://api.rynko.dev/api/mcp-documents
Rynko Flow	Validation Gateway	Validate AI agent outputs against schemas and business rules	https://api.rynko.dev/api/flow/mcp

Both servers use MCP Streamable HTTP transport and work with Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Zed, and Microsoft 365 Copilot.

---

Rynko Render MCP

Generate documents through natural conversation. Give your AI assistant access to your templates, and it can create draft templates, preview layouts, and generate production PDFs and Excel files.

Authentication: Personal Access Token (PAT)

→ Render MCP Setup & Tools

---

Rynko Flow MCP

Let AI agents validate their outputs before passing them to downstream systems. Each active gate generates a dedicated validate_{slug} tool with the gate's full schema and business rule descriptions.

Authentication: Workspace-scoped API Key

→ Flow MCP Setup & Tools

---

Using Both Servers Together

You can connect both servers simultaneously — they use different server names and credential types.

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "rynko": {
      "url": "https://api.rynko.dev/api/mcp-documents",
      "headers": {
        "Authorization": "Bearer pat_xxxxxxxxxxxxxxxx"
      }
    },
    "rynko-flow": {
      "url": "https://api.rynko.dev/api/flow/mcp",
      "headers": {
        "Authorization": "Bearer fm_your_api_key"
      }
    }
  }
}

Windsurf (~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "rynko": {
      "serverUrl": "https://api.rynko.dev/api/mcp-documents",
      "headers": {
        "Authorization": "Bearer pat_xxxxxxxxxxxxxxxx"
      }
    },
    "rynko-flow": {
      "serverUrl": "https://api.rynko.dev/api/flow/mcp",
      "headers": {
        "Authorization": "Bearer fm_your_api_key"
      }
    }
  }
}

VS Code (.vscode/mcp.json):

{
  "servers": {
    "rynko": {
      "type": "http",
      "url": "https://api.rynko.dev/api/mcp-documents",
      "headers": {
        "Authorization": "Bearer pat_xxxxxxxxxxxxxxxx"
      }
    },
    "rynko-flow": {
      "type": "http",
      "url": "https://api.rynko.dev/api/flow/mcp",
      "headers": {
        "Authorization": "Bearer fm_your_api_key"
      }
    }
  }
}

Claude Code:

claude mcp add --transport http rynko https://api.rynko.dev/api/mcp-documents \
  --header "Authorization: Bearer pat_xxxxxxxxxxxxxxxx"

claude mcp add --transport http rynko-flow https://api.rynko.dev/api/flow/mcp \
  --header "Authorization: Bearer fm_your_api_key"

note

The Render server uses a Personal Access Token (pat_*) while the Flow server uses a workspace-scoped API key (fm_*). These are different credential types — see each product's setup page for details.