# Copilot Studio → PDF with makesPDF

> For AI agents: a documentation index is available at https://makespdf.com/llms.txt — every docs page also has a markdown twin (append .md to the page URL), including this one: https://makespdf.com/docs/integrations/copilot-studio.md

[Microsoft Copilot Studio](https://www.microsoft.com/microsoft-copilot/microsoft-copilot-studio)
agents can connect to an MCP server with its **MCP onboarding wizard**. Add
makesPDF with API key authentication and the agent can render a PDF like any
other tool.

## Connect

You need a makesPDF
[API key](https://makespdf.com/settings/api-keys?ref=copilot-studio).

1. Open the agent's **Tools** page and select **Add a tool**, then **New tool**,
   then **Model Context Protocol** in the **Create new** section.
2. Fill in **Server name**, **Server description** and **Server URL**
   `https://makespdf.com/api/v1/mcp`. Write a clear description: Copilot Studio
   uses it to decide whether to call the server at runtime.
3. For the authentication type, choose **API key**, then set **Type of API key**
   to **Header**. Name the header `Authorization` and make the key value
   `Bearer <your key>`: the header has to carry the `Bearer` scheme, not the
   bare key.
4. Select **Create**. On the **Add tool** dialog, choose **Create a new
   connection**, then **Add to agent**.

**Streamable HTTP only.** makesPDF's MCP endpoint speaks Streamable HTTP, so there
is no SSE endpoint to configure.

## OAuth and data policies

Copilot Studio's other authentication type is **OAuth 2.0**, with **Dynamic
discovery**, **Dynamic** and **Manual** options. The two dynamic options register
a client with the server through dynamic client registration, which makesPDF does
not offer. **Manual** cannot work either: Copilot Studio generates its redirect URI
per tool (under `https://global.consent.azure-apim.net/redirect/`), so no client
registered in advance can cover it. The API key is the supported path.

Access to MCP servers goes through Power Platform connectors, so a data policy
that governs connectors also governs this server and its tools for your agent.

## Render a PDF

The agent sees each makesPDF tool with its description and chooses one at
runtime. Ask the agent for the document you want.

| Tool | Arguments | What it does |
| --- | --- | --- |
| `render_markdown` | `markdown`, optional `options` | Markdown → PDF (1 credit per 10 pages) |
| `render_template` | `templateId`, optional `data` | A stored or library template filled with your data |
| `validate_markdown` | `markdown` | Free accessibility check before you render |
| `list_templates` | optional `q`, `category`, `tags` | Find a library template such as `invoice-classic` |

The result carries `pageCount`, `creditsDeducted`, `artifactId` and a
`downloadUrl`.

## Get the file

`downloadUrl` is a signed link that needs no API key, so any step that can fetch
a URL can download the PDF, and the link is a field of the tool result the agent
returns.

The link expires 15 minutes after the render. To fetch an older render, call
`get_render_download_url` with its `artifactId` for a fresh link (free).

## Billing and limits

Renders bill your makesPDF credits exactly like the API: 1 credit per 10 pages
on success, nothing on failure. Validation and listing tools are free. On the
Free and Hobbyist plans, unless the account holds Growth credits, each page
carries a small makespdf.com link. Microsoft's own Copilot Studio and Power
Platform charges are separate. The full tool reference is on the
[MCP page](https://makespdf.com/docs/mcp).
