# LangSmith Fleet → 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/langsmith-fleet.md

[LangSmith Fleet](https://docs.langchain.com/langsmith/fleet/remote-mcp-servers)
agents can use remote MCP servers as tools. Add the makesPDF server once — to
one agent or to the whole workspace — and Fleet attaches the configured headers
to every tool discovery and every tool call.

## Connect

You need a makesPDF
[API key](https://makespdf.com/settings/api-keys?ref=langsmith-fleet) and the
**MCP Server Create** permission, which a workspace admin grants from workspace
settings.

1. For the whole workspace, open **Fleet** → **Integrations** and click
   **+ Custom MCP** at the bottom of the left sidebar. **Settings** →
   **MCP servers** and **Add server** is the same form.
2. For a single agent, open the agent, expand the **Connections** drawer, click
   **Add connection**, then **+ Add custom MCP**.
3. Enter a **Name** and the **URL** `https://makespdf.com/api/v1/mcp`.
4. Set **Authentication** to **Static Headers** and add one: key
   `Authorization`, value `Bearer <your key>`. That is the bearer-token pattern
   Fleet's docs give for a static header.
5. Save the server. Fleet discovers its tools and makes them available in your
   agents.

**OAuth needs client registration makesPDF does not offer.** Fleet's
**OAuth 2.1 (Auto)** registers a client through dynamic client registration, and
**OAuth 2.1 (Manual)** needs an OAuth provider registered in advance, with a
client that makesPDF would have to issue. Use **Static Headers**.

Keep the URL exactly as written: Fleet stores tool references by MCP server URL,
and its docs warn that changing the URL breaks agents that use that server's
tools until they are removed and re-added.

## Render a PDF

The tools appear alongside Fleet's built-in tools, so an agent uses them by
description. 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 client that can fetch
a URL can download the PDF; the field is part of the tool result the agent
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. LangSmith's own plan is billed separately. The
full tool reference is on the [MCP page](https://makespdf.com/docs/mcp).
