Office to PDF Skill

What this skill does

Office to PDF converts Word, Excel, PowerPoint, OpenDocument, RTF, text and CSV files to PDF and returns a download link valid for 2 days, with the page count of the result. Upload the file or send its URL. Paid plans can convert only selected pages and set landscape orientation. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Office to PDF Skill — exactly what your agent gets back when it makes the call.

vervekit · officetopdftool call

{
  "document": "https://raw.githubusercontent.com/apache/poi/trunk/test-data/document/SampleDoc.docx"
}

result

pdfName: 8f3c2a51-6d0e-4b7a-9c1f-2e5d7a9b4c10.pdf
inputName: SampleDoc.docx
inputFormat: docx
pageCount: 2
landscape: false
pageRanges: null
size: 23654
expires: 1792400000000

+1 more field

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

One toggle, a new capability

Enable Office to PDF and your app or agent can convert Office to PDF on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.

A tool agents call themselves

Over MCP, Office to PDF appears to your model as the officetopdf tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.

REST from any backend

Prefer to call it directly? Any language that can send a GET can hit Office to PDF to convert Office to PDF inline in your own server-side code.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

officetopdf

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/officetopdf

Ask your agent

“Enable Office to PDF and ask your agent to convert Office to PDF.”
“Use the Office to PDF skill for me.”

Office to PDF Skill, answered

How to connect it over MCP or REST.

How do I add Office to PDF to my app or agent?

Enable the Office to PDF Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the officetopdf tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to convert Office to PDF — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Office to PDF appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Office to PDF call cost?

Each call costs 30 credits. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Office to PDF is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Office to PDF is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

One toggle, a new capability

A tool agents call themselves

REST from any backend

Office to PDF Skill, answered

Other ways to use Office to PDF

Give your software a way to act on the world.

Scaling in production?