Pickle MCP Server

If you already use Pickle, the pickle mcp server is the piece that lets your assistant work with it directly. Free, local MCP server that audits ClickUp, Slack & Teams for work that slipped through.

What the server does

Pickle is a free, open-source AI ops manager for your team, packaged as an MCP server you run yourself. Give it your own ClickUp / Slack / Teams token, and your AI client (Claude, Cursor, Codex, Cline, Zed…) audits your workspace the way a sharp ops manager would: catching the work that quietly fell through.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Cost — Paid add-on

Credentials and setup notes

Configuration is passed through the environment: CLICKUP_API_KEY, SLACK_TOKEN, TEAMS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pickle's toolset — Cost — is a fair guide to whether it matches your workflow. It is maintained by adityaarsharma; worth a glance at recent repository activity before you build anything load-bearing on it.

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