Microsoft 365 Copilot

Connect Rynko Render to Microsoft 365 Copilot so your team can generate documents directly from Word, Teams, Outlook, and other M365 apps through natural conversation.

Server URL: https://api.rynko.dev/api/mcp-documents

Transport: Streamable HTTP (supported natively by Microsoft 365 Copilot)

Authentication: Personal Access Token (PAT) via API key header

---

How It Works

Microsoft 365 Copilot supports MCP servers as "actions" inside declarative agents. You create an agent that wraps the Rynko MCP server, deploy it to your M365 tenant, and your users can then ask Copilot to generate invoices, reports, or any other document template you've set up in Rynko — all without leaving Teams or Word.

The Rynko Render MCP server exposes 15+ tools that the agent can call: listing templates, creating drafts, previewing layouts, generating production PDFs, parsing spreadsheet data, and more. See the full tool list for details.

---

Prerequisites

• A Rynko account with at least one published template
• A Personal Access Token (PAT) — see Step 1 below
• Microsoft 365 Copilot license (required for users of the agent)
• One of the following, depending on your setup path:
  • Copilot Studio access (recommended for no-code setup)
  • VS Code with Microsoft 365 Agents Toolkit v6.3+ (for developer setup)

---

Step 1: Generate a Personal Access Token

1. Log in to your Rynko Dashboard
2. Go to Settings → Personal Access Tokens
3. Click Create Token
4. Enter a label (e.g., "Microsoft 365 Copilot")
5. Select expiry (max 30 days)
6. Click Create and copy the token immediately — it won't be shown again

warning

Keep your PAT secure. Anyone with this token can access your templates across all environments. Set a calendar reminder to rotate the token before it expires.

---

Setup Options

There are two ways to connect Rynko to Microsoft 365 Copilot. Choose the one that fits your team:

Approach	Best For	Tools Needed
Copilot Studio	Admins and non-developers	Browser only
Declarative Agent	Developers who want version control	VS Code + Agents Toolkit

Copilot Studio (Recommended)

Option A: Copilot Studio

The quickest way — no code required. You connect the Rynko MCP server through the Copilot Studio wizard and deploy the agent to your M365 tenant.

Step 2: Create an Agent in Copilot Studio

1. Open Copilot Studio
2. Create a new agent (or open an existing one)
3. Give it a name like "Rynko Document Generator" and a description:

   Generate PDF and Excel documents from Rynko templates. Can list templates, preview layouts, and generate production documents.

Step 3: Add the Rynko MCP Server

1. Go to the Tools page for your agent
2. Click Add a tool → New tool → Model Context Protocol
3. Fill in the MCP onboarding wizard:

Field	Value
Server name	Rynko Render
Server description	Generate PDF and Excel documents from templates. List templates, preview layouts, parse spreadsheet data, and generate production documents.
Server URL	https://api.rynko.dev/api/mcp-documents
Authentication	API key

4. For API key configuration:
   • Type: Header
   • Header name: Authorization
5. Click Create

Step 4: Create a Connection

1. On the Add tool dialog, select Create a new connection

2. Enter your PAT value in the format: Bearer pat_xxxxxxxxxxxxxxxx

   warning

   Include the Bearer prefix before your token.

3. Click Add to agent

Step 5: Test and Publish

1. Use the Test panel in Copilot Studio to verify:
   • "List my templates"
   • "Generate a preview of my invoice template"
2. Once confirmed working, click Publish to make the agent available in your M365 tenant
3. Users can find the agent in the Agents section of Microsoft 365 Copilot at m365.cloud.microsoft/chat

Declarative Agent (VS Code)

Option B: Declarative Agent via VS Code

For developers who want the agent in source control. Uses the Microsoft 365 Agents Toolkit to scaffold a declarative agent that wraps the Rynko MCP server.

Step 2: Create the Agent Project

1. Open VS Code and select the Microsoft 365 Agents Toolkit icon in the Activity Bar
2. Click Create a New Agent/App
3. Select Declarative Agent → Add an Action → Start with an MCP Server
4. Enter the Rynko server URL:

   https://api.rynko.dev/api/mcp-documents

5. Choose a project folder and enter a name (e.g., "Rynko Document Generator")

The toolkit generates the agent project files.

Step 3: Configure Authentication

Open .vscode/mcp.json in the generated project and update it:

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

Step 4: Select Tools

1. Open .vscode/mcp.json and click the Start button in the editor
2. Click ATK: Fetch action from MCP → select ai-plugin.json
3. Choose which Rynko tools to expose. Recommended starting set:
   • list_templates — List available templates
   • get_template — Get template details and variables
   • preview_template — Generate a preview document
   • generate_document — Generate a production document
   • get_job_status — Check generation progress
   • parse_data_file — Parse Excel/CSV data
4. Select API key as the authentication type

Step 5: Deploy to Microsoft 365

1. In the Agents Toolkit, go to Accounts → Sign in to Microsoft 365
2. Verify Custom App Upload Enabled and Copilot Access Enabled are shown
3. In Lifecycle, click Provision
4. When prompted for credentials, enter your PAT
5. Wait for provisioning to complete

Step 6: Test the Agent

1. Go to m365.cloud.microsoft/chat
2. Find your agent in the Agents sidebar (it'll have dev appended)
3. Try: "List my document templates" or "Generate an invoice for Acme Corp"

---

Example Conversations

Once deployed, your team can interact with Rynko through natural conversation in Microsoft 365 Copilot:

User: Generate an invoice for Globex Corp, $12,500 for consulting services, due March 30th.

Copilot: I'll use your invoice template to generate that. Let me check the required variables...

[Calls list_templates, then generate_document]

Your invoice has been generated. Here's the download link: [Invoice-Globex-Corp.pdf]

User: I have a spreadsheet of customers. Can you generate reports for each one?

Copilot: Sure, share the file and I'll map the columns to your report template.

[Calls parse_data_file, then map_variables, then generate_document for each row]

---

What Your Team Can Do

Capability	Example Prompt
List templates	"What document templates do I have?"
Preview a template	"Show me a preview of the quarterly report template"
Generate a document	"Generate an invoice for Acme Corp, $5,000 USD"
Parse data files	"I have this Excel file — can you map it to my template?"
Create draft templates	"Create a new invoice template with company logo, line items, and payment terms"
Check job status	"Is my batch generation done yet?"

tip

Templates created via MCP are always saved as drafts. Your team can review and publish them from the Rynko dashboard — the AI can't push to production directly.

---

Security Considerations

• PAT Expiry: Tokens expire after max 30 days. Set a reminder to rotate them.
• Draft-Only Safety: AI-created templates are drafts until a human publishes them.
• Audit Trail: All MCP operations are logged in your Rynko activity feed.
• Tenant Scoping: The agent is deployed to your M365 tenant — only authorized users can access it.
• No Credential Sharing: With Copilot Studio's API key auth, the PAT is stored in the connection — end users don't see or need to know it.

---

Limitations

• Preview status: MCP plugins for Microsoft 365 Copilot are currently in public preview.
• Nested objects: M365 manifest validation may reject tools with deeply nested object parameters. If provisioning fails, try selecting fewer tools or contact support.
• SSE not supported: Copilot Studio dropped SSE transport support (August 2025). Rynko uses Streamable HTTP, which is fully supported.
• License required: End users need a Microsoft 365 Copilot license to interact with the agent.

---

Troubleshooting

"Invalid token" or authentication errors

• Ensure the PAT starts with pat_ and hasn't expired
• In Copilot Studio, verify the connection value is Bearer pat_xxx (with the Bearer prefix)
• Generate a fresh token from the Rynko dashboard

Agent doesn't appear in M365 Copilot

• Verify your M365 account has Custom App Upload and Copilot Access enabled
• Wait a few minutes after provisioning — propagation can take time
• Check with your M365 admin if custom agents are allowed in your tenant

Tools not loading

• Confirm the server URL is exactly https://api.rynko.dev/api/mcp-documents
• Test the PAT by calling the server directly with curl:

  curl -X POST https://api.rynko.dev/api/mcp-documents \
    -H "Authorization: Bearer pat_xxxxxxxxxxxxxxxx" \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

---

Related: Render MCP (full tool reference) | Flow MCP | MCP Overview