# CrewAI AMP → 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/crewai-amp.md

[CrewAI AMP](https://app.crewai.com) is CrewAI's hosted platform. It can add any
remote MCP server as a **connection**, and that server's tools can then be
assigned to agents in your crews. This is a different integration from the
`makespdf[crewai]` Python extra, which wraps the makesPDF API as two BaseTools
inside a CrewAI process: this page is the platform path.

## Connect

You need a makesPDF
[API key](https://makespdf.com/settings/api-keys?ref=crewai-amp). The server you
add has to be reachable from the internet and support Streamable HTTP; makesPDF
is both.

1. In CrewAI AMP, open **Tools & Integrations** in the left sidebar and select
   the **Connections** tab.
2. Click **Add Custom MCP Server**.
3. Fill in a **Name**, an optional **Description**, and the **Server URL**
   `https://makespdf.com/api/v1/mcp`.
4. Choose **Authentication Token**. Set **Header Name** to `Authorization` and
   **Value** to `Bearer <your key>`; that is the form CrewAI's docs give for a
   server that expects a Bearer token.
5. Leave **Add to** on **Header**, then click **Create MCP Server**.
6. The connection appears in the Connections list, and its tools appear on the
   **Tools & Integrations** page with the built-in connections.

**OAuth 2.0 needs a client registered with us.** CrewAI's other authentication
method is OAuth 2.0, which takes a client ID issued by the provider, so it needs
an OAuth client registered with makesPDF. Use the authentication token today.

## Render a PDF

Assign the makesPDF tools to agents in your crews like any other CrewAI tool, then
describe 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 anything that can fetch
a URL can download the PDF, and the link is in the tool result the crew run
records.

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).

## CrewAI in code

If your agents run in a CrewAI process you control, the Python extra is the
better fit: two BaseTool wrappers over the hosted API, installed with
`pip install "makespdf[crewai]"`. See
[CrewAI → PDF](https://makespdf.com/docs/integrations/crewai) for that path. The two can be
used together — an AMP crew can call a Python tool service that uses the extra.

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