# Viktor → 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/viktor.md

[Viktor](https://viktor.com/) connects to a remote MCP server as a **Custom
integration** of type **MCP Server**, and the server's tools then work wherever
you talk to Viktor — Slack, Microsoft Teams, email or the web app. Connect
makesPDF by URL and enter the key when **Detect automatically** asks for it.

## Connect

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

1. In Viktor, open **Integrations** and select **Add Custom**.
2. Choose **MCP Server** and select **Next**.
3. Enter the **Server URL** `https://makespdf.com/api/v1/mcp`, including
   `https://`.
4. Keep **Authentication** on **Detect automatically** and select **Connect**.
   Viktor works out how the server authenticates, and when it needs an API key a
   page asks you for the key: paste your makesPDF key there.
5. Give the connection a nickname, and in a Slack or Microsoft Teams workspace
   choose who can use it.
6. The connection is ready. Ask Viktor for a PDF and it calls the makesPDF tools.

**HTTPS only, remote only.** Viktor connects only to remote MCP servers that are
reachable over HTTPS; local servers running on your machine and private or
internal network addresses are not supported. makesPDF is public HTTPS.

## If Viktor mentions OAuth

Viktor's **Authentication** list also has an explicit **API key** choice: choose it
when you would rather paste the key yourself than let Viktor detect it, or when
detection does not offer a key prompt. The other two choices, **Sign in with your
own OAuth app** and **Client ID and secret, no sign-in**, both need an OAuth client
that makesPDF would have to issue, so neither is available yet.

If a connection reports that the server does not support automatic OAuth client
registration, Viktor has found the server's OAuth metadata and no registration
endpoint. Reconnect and set **Authentication** to **API key**, then paste your
makesPDF key.

## Render a PDF

Viktor chooses among the connection's tools by their descriptions, so ask for the
document you want and it calls the tool that renders it.

| 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 client that can fetch
a URL can download the PDF; the field is part of the tool result Viktor receives.

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. Viktor's own plan is billed separately. The
full tool reference is on the [MCP page](https://makespdf.com/docs/mcp).
