PDF4me AI & SDKs
PDF4me AI & SDKs is the developer-library side of these docs: the official clients you install into your own code, plus the two ways an AI assistant can call PDF4me for you. Every option here wraps the same 106 document actions across the same 18 sections as the REST API.
If you are building a no-code flow in Power Automate, Zapier, Make or n8n instead, those connectors live under Integrations.
Which one should you use?
| Option | Use it when | Install |
|---|---|---|
| PDF4me MCP | You want Cursor, Claude Desktop, VS Code or Windsurf to run PDF actions for you | uvx |
| PDF4me Python SDK | You write Python 3.11+ apps, scripts or notebooks | pip install pdf4me |
| PDF4me JavaScript SDK | You write TypeScript or ESM JavaScript on Node.js 22+ | npm install pdf4me@^10 |
| PDF4me .NET SDK | You write C# on .NET 8+ or .NET Framework 4.6.2+ | dotnet add package Pdf4me.Client |
| PDF4me Agent Skills | You want a coding agent to know the REST API without an MCP server | npx skills add |
The three language SDKs expose the same action names with the same defaults, so a flow prototyped in one translates directly to another.
What about the REST API?
Every option on this page is a client for the same service. If your language has no official SDK yet, call the PDF4me REST API directly, or start from the public code samples on GitHub, which cover C#, Java, Python, JavaScript and Salesforce Apex.