Skip to main content

Connect PDFBolt to Other MCP Clients

Use PDFBolt with a compatible MCP client to generate PDFs from prompts, web page URLs, or reusable templates.

For Claude, Claude Code, Codex, or Cursor, follow the dedicated setup guide.

Before You Start​

You need a PDFBolt account and an MCP client that supports remote servers over Streamable HTTP with a compatible OAuth sign‑in flow.

1. Add the PDFBolt MCP Server​

Add a remote MCP server named PDFBolt using this URL:

https://api.pdfbolt.com/mcp

Follow your client's documentation to add the server. Configuration fields and file locations vary by client.

If prompted, choose Streamable HTTP as the transport and OAuth for authentication. You do not need a PDFBolt API key.

2. Sign In and Allow Access​

Use your client's authentication option to connect your PDFBolt account. Sign in to PDFBolt in your browser if prompted.

Review the requested permissions and select Allow access. Return to your client and enable PDFBolt's tools if required.

3. Check the Connection​

Open a conversation that can use MCP tools and send:

Use PDFBolt to check my current plan and remaining credits. Do not generate any PDFs.

Approve the request if prompted. The response should show your plan and remaining credits. Checking usage does not consume PDF generation credits.

4. Generate a PDF​

Ask your assistant to convert a web page to PDF using the URL as the source:

Use PDFBolt to convert https://example.com to an A4 PDF. Use the URL directly as the source. Give me a PDF download link.

Open the returned link in your browser to view the document. Support for PDF attachments and saving files depends on your client.

Troubleshooting​

The client cannot connect to PDFBolt

Check that the server URL is https://api.pdfbolt.com/mcp and that your client supports Streamable HTTP and OAuth. If you cannot find an OAuth sign-in option, check your client's documentation for remote MCP setup.

An error mentions dynamic client registration

Check your client's documentation to see whether you can configure a published OAuth Client ID URL. Use the URL provided by your client. Do not substitute a PDFBolt API key or another app's Client ID.

Clients that require dynamic registration and offer no alternative cannot connect to PDFBolt.

The connection works, but the assistant does not use PDFBolt

Check that PDFBolt's tools are enabled in the conversation. Mention PDFBolt in your prompt and approve the tool request if your client is waiting for permission.

For other errors, see the MCP troubleshooting guide.