Putio MCP Server

MCP server for interacting put.io. Exposed over MCP by the putio mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Don't forget to replace <your-putio-api-token> with your own API token.

• List active transfers
• Add new transfers via URL or magnet link
• Cancel existing transfers
• Get browser links for completed transfers

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need one environment variable: PUTIO_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Claude Desktop - Python 3.x - uvx - Put.io account and API token (guide)

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by putdotio; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Putio's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the putio mcp server does with a few real requests.