Connect your AI Agents to Adobe PDF Services in minutes

What is an Adobe PDF Services MCP?

It's an MCP server that gives your agents access to PDF creation, conversion, and document processing capabilities from Adobe PDF Services via tools. Your agents can invoke these tools to convert files to and from PDF, extract text and structured data from documents, generate PDFs from templates, apply password protection, and more.

Adobe doesn't offer an MCP server purpose built for PDF Services, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Adobe PDF Services MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated contract generation: When a deal is marked closed-won in your CRM, an agent pulls the account and deal fields, populates a contract template in Adobe PDF Services, and sends the generated PDF to the customer via email, eliminating manual document assembly

• Invoice data extraction pipeline: When a vendor uploads an invoice PDF to a designated folder, an agent calls Adobe PDF Services to extract structured line-item data, then writes the parsed fields to your ERP or accounting system without manual entry

• Compliance report packaging: On a monthly schedule, an agent pulls report data from multiple internal sources, converts each output to PDF, merges them into a single combined document, and delivers it to the compliance team's shared drive

• Document redaction workflow: When a support ticket references a sensitive document, an agent retrieves the file, applies redaction rules via Adobe PDF Services to mask regulated fields, and returns the sanitized version for sharing with external parties

What are popular tools for Adobe PDF Services's MCP server?

Here are some of the most commonly used tools:

• create_pdf: converts a source file (Word, Excel, HTML, or image) into a PDF document. Useful for agents that generate reports or contracts from structured data and need a portable, finalized output format

• export_pdf: converts an existing PDF to a target format such as DOCX, XLSX, or PPTX. Call this when an agent needs to extract editable content from a PDF for downstream processing or analysis

• extract_pdf: pulls structured text, tables, and element metadata from a PDF using the Extract API. Good for workflows where an agent needs machine-readable data from a scanned or native PDF without manual parsing

• merge_documents: combines multiple PDF files into a single document in a specified order. Use this when an agent needs to assemble a final package from several generated or collected files

• protect_pdf: applies password protection and permission restrictions to a PDF. Helpful when an agent needs to secure a generated document before delivering it to an external recipient

• generate_document: produces a PDF or Word document by merging dynamic data into a predefined template using the Document Generation API. Use this when an agent is creating personalized contracts, proposals, or reports from structured records

What makes Merge Agent Handler's Adobe PDF Services MCP server better than alternative Adobe PDF Services MCP servers?

A few things distinguish Merge Agent Handler's Adobe PDF Services MCP server from community implementations or self-built alternatives:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Adobe PDF Services, this means document contents, extracted text from confidential files, and template data containing personal or financial information can be filtered at the tool layer even when the agent has broad access

• Managed authentication and credentials: Merge stores your Adobe PDF Services API credentials and handles all token management. You never embed client secrets or OAuth tokens in agent configuration or coordinate credential rotation manually

• Real-time observability and audit trail: Every Adobe PDF Services tool call is captured with timestamp, tool name, input parameters, and response metadata. Compliance and security teams can audit exactly which documents an agent processed, converted, or extracted without adding custom instrumentation

• Tool Packs and controlled access: Tool Packs let you bundle specific Adobe PDF Services tools with tools from other connectors into a single MCP endpoint scoped to a use case. An extraction agent gets only the tools it needs for parsing. A generation agent gets only template and merge tools. Neither can reach operations outside its defined scope

How can I start using Merge Agent Handler's Adobe PDF Services MCP server?

You can take the following steps (this is assuming you use Claude Code):

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Adobe PDF Services and complete the auth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start invoking Adobe PDF Services tools directly. The first time you use an Adobe PDF Services tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Adobe PDF Services MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge Agent Handler to connect their AI tools to Adobe PDF Services?

Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, Codex, and other MCP-compatible AI tools to Adobe PDF Services without bypassing IT governance.

Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity. A legal ops coordinator, for instance, can ask their AI to generate a contract PDF from a template, merge signature-ready documents, or extract clause data from an uploaded agreement, all without IT losing visibility into which files were processed.

IT also provisions access by role or group via SCIM. A legal ops coordinator, for example, gets Adobe PDF Services access to generate and merge contract documents, DocuSign to manage signature workflows, and Google Drive to store finalized files; while a finance analyst gets Adobe PDF Services access to extract data from invoices, NetSuite to reconcile transactions, and Slack to report processing results.

Every tool call an employee's AI makes to Adobe PDF Services is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.