pastebox-mcp

MCP server for Pastebox — lets any MCP-compatible agent (Claude Code, Cursor, Codex, …) push output into your Pastebox and get back a shareable URL, instead of dumping long logs/diffs into the chat.

Run

npx -y pastebox-mcp

It speaks MCP over stdio. Configure it in your agent and point it at your Pastebox with env vars.

Configuration

| Env | Required | Default | Notes | |-----|----------|---------|-------| | PASTEBOX_URL | recommended | http://localhost:3000 | Your Pastebox base URL, e.g. https://paste.example.com | | PASTEBOX_API_KEY | recommended | — | An API key (pb_…). Without it you hit anonymous rate limits and list_pastes won't work. |

Env vars win over ~/.pastebox.json (the file the pastebox CLI writes via pastebox config), so you can rely on either.

Claude Code

claude mcp add pastebox --env PASTEBOX_URL=https://paste.example.com --env PASTEBOX_API_KEY=pb_… -- npx -y pastebox-mcp

or in .mcp.json:

{
  "mcpServers": {
    "pastebox": {
      "command": "npx",
      "args": ["-y", "pastebox-mcp"],
      "env": { "PASTEBOX_URL": "https://paste.example.com", "PASTEBOX_API_KEY": "pb_…" }
    }
  }
}

Cursor — .cursor/mcp.json

{
  "mcpServers": {
    "pastebox": {
      "command": "npx",
      "args": ["-y", "pastebox-mcp"],
      "env": { "PASTEBOX_URL": "https://paste.example.com", "PASTEBOX_API_KEY": "pb_…" }
    }
  }
}

Codex — ~/.codex/config.toml

[mcp_servers.pastebox]
command = "npx"
args = ["-y", "pastebox-mcp"]
env = { PASTEBOX_URL = "https://paste.example.com", PASTEBOX_API_KEY = "pb_…" }

Tools

• create_paste — store text and return a view URL. Inputs: content (required), title, syntax, ttlSeconds, burnAfterRead.
• get_paste — fetch a paste's content by publicId.
• list_pastes — list recent pastes for the configured API key.

⚠️ Encryption

create_paste does not encrypt content — it is not end-to-end encrypted. For secrets (tokens, .env values, private keys) do not use this MCP tool; use the pastebox CLI with --e2ee --burn, which encrypts client-side before upload (the key stays in the URL fragment and never reaches the server). E2EE support in the MCP server is planned for a future version.