← Back to directory
P

Pare Bun

Community
Structured JSON output for Bun runtime operations
GitHub source repository ↗
★ 138 Stars Category · Dev Tools Popular Source revision 57e1980e8375
26FMRS · D
Reliability
4/20
Security and permissions
5/20
Maintenance
6/20
Documentation
5/20
Setup experience
6/20

Pare Bun is a package within the Pare collection, focused on turning Bun operations into structured JSON to improve AI agent efficiency. It is third-party, not an official Bun project. Users should be aware of command side effects and version compatibility.

Read the FMRS scoring method →

Pare Bun is an MCP server from the Pare project that wraps Bun runtime operations into typed, schema-validated JSON, replacing fragile terminal text parsing. Using MCP's structuredContent and outputSchema features, it provides reliable, directly actionable data for AI agents, reducing token usage and enhancing cross-platform compatibility.

Tools

The tool list has not been reviewed yet.

Setup

  1. Configure your MCP client to launch the server with the command 'npx -y @paretools/bun'; 2. Optionally restrict tools via the environment variable PARE_BUN_TOOLS; 3. Restart your client session.
claude_desktop_config.json
{
  "mcpServers": {
    "pare-bun": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/bun"
      ],
      "env": {
        "PARE_BUN_TOOLS": ""
      }
    }
  }
}

Fit and risk

Best for

  • Projects using Bun as the JavaScript runtime and package manager
  • Teams relying on AI agents for coding, building, and testing automation
  • Developers focused on token efficiency and output reliability

Not for

  • Scenarios that do not require Bun or structured output
  • Use cases needing other runtime tools
  • Environments that rely on interactive terminal output

Required permissions

  • Permissions to execute Bun commands
  • Read and write access to project files (depending on usage)
  • Network access for downloading packages or interacting with remote repositories as needed

Risks and side effects

  • Executing Bun commands may have side effects such as modifying files or installing packages
  • Output schemas could change with version updates, potentially breaking existing agent logic
  • Not maintained by Bun's upstream project; compatibility issues may arise

Troubleshooting

  1. Ensure Node.js version >= 20
  2. If npx fails, try installing '@paretools/bun' globally or use an absolute path
  3. If connection timeouts occur, increase MCP_TIMEOUT in your client config
  4. Check whether environment variable PARE_BUN_TOOLS limits tools, potentially making the server unusable

Use cases

AI agents that need to run Bun operations (e.g., installing packages, running scripts) and consume structured output directly
Automated development workflows aiming to reduce token consumption
Development environments requiring consistent, cross-platform command output

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS Code / CopilotFull support
WindsurfFull support
Cline / Roo CodeFull support
OpenAI CodexFull support
Gemini CLIFull support
ZedFull support
Continue.devFull support