put.io MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@put.io MCPwhat's my current storage usage?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
put.io MCP
Private TypeScript MCP service for conversationally managing authorized content in one put.io account.
The repository is in pre-implementation planning and risk retirement. It does not yet expose working MCP tools, authenticate ChatGPT, or mutate put.io.
Local setup
Requirements:
Node.js 24.19.0 or newer
pnpm 11.19.0
pnpm install --frozen-lockfile
cp .env.example .dev.vars
pnpm devThe local health endpoint is http://localhost:8787/health. The Streamable HTTP MCP endpoint is http://localhost:8787/mcp. During the transport spike it exposes only get_storage, which safely returns PUTIO_UNCONFIGURED without a put.io credential or live API request.
Verification
pnpm lint
pnpm typecheck
pnpm test
pnpm test:contract
pnpm build
pnpm build:sdk-spikeNever commit .dev.vars, tokens, OAuth codes, raw magnets, release URLs, account data, or real media filenames.
See AGENTS.md, docs/STATUS.md, and docs/threat-model.md before changing behavior.
This server cannot be deployed
Maintenance
Related MCP Connectors
Notes, files, GitHub, and Drive through one MCP connection.
Notes, files, GitHub, and Drive through one MCP connection.
Notes, files, GitHub, and Drive through one MCP connection.
Read and write shared BitsWeave context, projects, tasks, and work sessions through MCP.