I kept hitting the same tiny annoyance. I would be deep in a chat with Claude, working through some documents, and then I would need one of them as a Word file. Or a client would send a HEIC photo that nothing wanted to open. Every time it meant leaving the editor, finding a converter site, uploading, downloading, and coming back. Small friction, but it adds up over a day.
So I wired the conversion step directly into the assistant using MCP. Now I just ask for it in plain language and the file lands in my folder. This post shows how to set that up.
What MCP gives you here
The Model Context Protocol lets an AI client call external tools in a structured way. Instead of the model guessing or writing throwaway scripts, it calls a real tool with real arguments and gets a real result back. A conversion server is a good fit: the model does not need to know how to render a PDF, it just needs to know that a convert_file tool exists and what it accepts.
I used the Convertica MCP server because it wraps a whole batch of conversions behind two tools, but the pattern applies to any MCP server you like.
