Guides
Ecosystem: CLI, editors, CI
The MCP server is one door into Pastepile. The CLI, VS Code extension, GitHub Action, and REST API read and write the same pastes.
1 min read · Updated
Everything below talks to the same API and the same pastes, so knowledge saved by an assistant is instantly reachable from your terminal, editor, and CI, and vice versa.
CLI
npm i -g pastepile installs a zero-dependency command-line client (Node 18+). Create from stdin or files, read raw content to stdout, list, and delete:
cat error.log | pastepile --title "build error" --expiry 1d pastepile get aB3xY9z > restored.txt
VS Code extension
Paste the current selection, file, or clipboard without leaving the editor. The API key lives in VS Code SecretStorage, never in settings files, and the paste URL lands on your clipboard.
GitHub Action
Publish a file, CI log, or arbitrary text from a workflow and get the paste URL as a step output; on pull_request events it can post the URL as a PR comment. Ideal for surfacing failing test logs that an assistant later reads with `pastepile_get`.
REST API and OpenAPI
The REST API docs cover every endpoint the MCP server wraps, plus the write-by-edit-key operations it does not (update, delete). A machine-readable OpenAPI spec is available for codegen.
Developer Toolbox
/tools is the in-browser complement: dozens of offline encode, decode, hash, and format tools, composable into workflows, with paste loading built in.