Skip to main content
ClaudeWave

Free, local, open-source MCP server that audits your ClickUp, Slack & Teams for what fell through the cracks — stale tasks, dropped promises, decisions lost in DMs. No account, no telemetry. Works in Claude, Cursor, Codex, Cline, Zed.

MCP ServersRegistry oficial3 estrellas0 forksJavaScriptMITActualizado today
Install in Claude Code / Claude Desktop
Method: Manual
Claude Code CLI
git clone https://github.com/adityaarsharma/pickle
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "pickle": {
      "command": "node",
      "args": ["/path/to/pickle/dist/index.js"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
💡 Clone https://github.com/adityaarsharma/pickle and follow its README for install instructions.
Casos de uso

Resumen de MCP Servers

# 🥒 Pickle: the free AI ops manager for ClickUp, Slack & Teams

![Pickle: catch what slips through ClickUp, Slack and Teams. The AI ops manager that catches what your team dropped](docs/pickle-cover.png)

> **ClickUp Brain reads your tasks. Slack AI reads your messages. Both are paid add-ons, and each only sees its own app.**
> **Pickle is a free AI ops manager that runs on your own machine, reads across all three, and tells you what slipped through: stale tasks, dropped promises, decisions buried in a DM.**

[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](LICENSE)
[![MCP compatible](https://img.shields.io/badge/MCP-compatible-7c3aed?style=flat-square)](https://modelcontextprotocol.io)
[![No account · no telemetry](https://img.shields.io/badge/no%20account-no%20telemetry-22c55e?style=flat-square)](#privacy)
[![Works with](https://img.shields.io/badge/works%20with-Claude·Cursor·Codex·Cline·Zed-f97316?style=flat-square)](#works-with)
[![Star this repo](https://img.shields.io/github/stars/adityaarsharma/pickle?style=flat-square&color=eab308)](https://github.com/adityaarsharma/pickle/stargazers)

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.

**No account. No hosted server. No key from us. No telemetry.** Pickle adds no middleman. It talks only to *your* tools, with *your* token. Nothing is sent to us, because there's no "us" to send it to.

> ⭐ **Pickle is free and will stay free. There is no paid tier.** If you think workspace tools should run on your own machine, **star the repo.** Stars are the only way it gets found.

---

## <a id="privacy"></a>Why this is different

| | ClickUp Brain | Slack AI | **Pickle** |
|---|---|---|---|
| Sees **across** your tools | ❌ ClickUp only | ❌ Slack only | ✅ ClickUp + Slack + Teams |
| Where your data flows | Their cloud | Their cloud | **Only to your own tools, with your token** |
| A third party holds your token | Yes | Yes | **No, it stays in your local config** |
| Cost | Paid add-on | ~$10/user/mo | **Free · MIT · open source** |
| You can read every line | ❌ | ❌ | ✅ it's all right here |

Honest version of the privacy claim: Pickle *does* read your ClickUp/Slack/Teams. That's the job. But it reads them **directly, from your machine, with your token**, and sends nothing to any Pickle server. Verify it yourself. The code is in [`server-remote/server.mjs`](server-remote/server.mjs), and there is no analytics, no beacon, no phone-home.

---

## <a id="install"></a>Install: one command

Guided: it asks which tools you use, points you to where each token lives, and writes your MCP config for you.

```bash
curl -fsSL https://pickle.adityaarsharma.com/install.sh | bash
```

**Or add it to your MCP client yourself** (via [npm](https://www.npmjs.com/package/pickle-mcp)):

```json
{
  "mcpServers": {
    "pickle": {
      "command": "npx",
      "args": ["-y", "pickle-mcp"],
      "env": { "CLICKUP_API_KEY": "pk_your_own_token" }
    }
  }
}
```

Add `SLACK_TOKEN` (`xoxp-…`) and/or `TEAMS_TOKEN` to the same `env` block to switch on the cross-tool patterns. Restart your client. `npx` runs it locally on your machine, no global install, no clone.

The installer asks which tools you use (ClickUp / Slack / Teams), takes the token *you already have* for each, and writes the MCP config for your client automatically. No hand-editing, no key from us.

> Prefer to do it by hand? See [`docs/manual-install.md`](docs/manual-install.md). The only token you ever provide is your own platform token (e.g. ClickUp `pk_…` from Settings → Apps).

Then just ask your AI:

> *"Pickle, run my morning audit: scan my ClickUp from the last 7 days and show me the 3 worst things I missed, worst first."*

---

## What it catches

- **Stale in-progress**: "doing" for days, zero activity
- **Dropped promises**: "I'll do X by Friday" with no follow-through
- **Decisions buried in DMs**: a call made in a thread that never became a task
- **Delegations nobody chased**: you asked, it never landed, everyone forgot
- **Standup copy-paste**, zombie tasks, empty-description work, blocker rot… full list in [`docs/patterns.md`](docs/patterns.md)

---

## <a id="works-with"></a>Works with

Claude Code · Claude Desktop · Cursor · Codex · Cline · Continue · Zed · any MCP host. The reasoning runs in **your** model. Pickle just fetches and structures the data. Optional [Claude Code skills](docs/skills.md) add `/pickle-*` slash commands as a convenience layer.

---

## Free, and what I ask instead of money

Pickle has no paid tier and never will. Instead:

- ⭐ **Star the repo** if it caught even one thing worth fixing. A free tool has no ad budget, so a star is genuinely how the next person finds it.
- 📮 **[Get update notes + workspace-AI tips](https://adityaarsharma.com)**: occasional, practical notes on using AI in real team workflows (the same patterns Pickle runs). Reply anytime with a suggestion or a pattern you want added. I read every one.

### 🧭 Want your team to actually *use* AI well?

Pickle is what I use to keep my own team honest. If you're rolling AI into how your company works (onboarding people onto it, wiring it into real workflows, choosing which LLM for what), **[reach out to me](https://adityaarsharma.com/?src=pickle-readme)**. I help teams go from "we bought AI licenses" to "AI is actually in our workflow," with real use-cases instead of hype.

Built in the open by **[Aditya Sharma](https://adityaarsharma.com)**, a marketer who codes.

## FAQ

**Is Pickle really free?**
Yes. MIT-licensed, no paid tier, no account, no credit card. I built it in the open; a ⭐ is the only thing I ask.

**Do I need a Pickle account or an API key from you?**
No. Pickle issues nothing. The only token you provide is your *own* ClickUp / Slack / Teams token, and it lives in your local MCP config.

**Does my data get sent to you or to any cloud?**
No middleman. Pickle runs on your machine and talks only to *your* tools (ClickUp / Slack / Microsoft Graph) using *your* token. There is no Pickle server, no telemetry, no phone-home. Pickle does read your ClickUp/Slack/Teams (that's the job), but it sends nothing to us. Verify it in [`server-remote/server.mjs`](server-remote/server.mjs).

**Which AI clients does it work with?**
Any MCP-compatible host: Claude Code, Claude Desktop, Cursor, Codex, Cline, Continue, Zed, and more. The reasoning runs in *your* model.

**What should I ask Pickle first?**
After installing, restart your AI client and paste: *"Pickle, run my morning audit: scan my ClickUp from the last 7 days and show me the 3 worst things I missed, worst first."* You get a ranked, punchy result instead of a data dump, so you feel the value on the first run.

**How is this different from ClickUp Brain or Slack AI?**
Those are cloud add-ons that each see only their own tool and send your data to their servers. Pickle runs locally, reads *across* ClickUp + Slack + Teams, and keeps your token on your machine. Different axis: privacy + cross-tool, not "more features."

**Is it safe to give it my token?**
The token stays in your local config file (`chmod 600`), and the code is open. Read it before you connect. Nothing is transmitted anywhere except the platform's own API.

**Will Pickle change or delete anything in my tools?**
By default it only reads and reports, it does not touch your data. It can create a reminder or drop a comment if you explicitly ask it to (for example "remind me about XYZ-184"), but the audit itself is read-only. You stay in control.

**Do I need Slack and Teams too, or is ClickUp enough?**
ClickUp alone is a great start. Slack/Teams unlock the cross-tool patterns (decisions-in-DMs, ghost mode) because those need chat data.

**Can it audit GitHub or other tools?**
Not yet. A GitHub audit (stale PRs, dropped reviews) is a planned/welcome contribution.

**Is there a hosted version?**
No. Pickle is local by design. If you want your team to adopt AI tools like this well, [reach out](https://adityaarsharma.com). That's the consulting I do.

## Contributing

Issues and PRs welcome: new patterns, new connectors (a GitHub audit for stale PRs is a great first one), better client configs.

## License

MIT © [Aditya Sharma](https://adityaarsharma.com)
ai-agentai-agentsai-toolsautomationclickupcodexcursordeveloper-toolsllmllm-agentlocal-firstmcpmcp-servermcp-toolsmicrosoft-teamsmodel-context-protocolprivacyself-hostedslackteam-management

Lo que la gente pregunta sobre pickle

¿Qué es adityaarsharma/pickle?

+

adityaarsharma/pickle es mcp servers para el ecosistema de Claude AI. Free, local, open-source MCP server that audits your ClickUp, Slack & Teams for what fell through the cracks — stale tasks, dropped promises, decisions lost in DMs. No account, no telemetry. Works in Claude, Cursor, Codex, Cline, Zed. Tiene 3 estrellas en GitHub y se actualizó por última vez today.

¿Cómo se instala pickle?

+

Puedes instalar pickle clonando el repositorio (https://github.com/adityaarsharma/pickle) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar adityaarsharma/pickle?

+

adityaarsharma/pickle aún no ha sido auditado por nuestro agente de seguridad. Revisa el repositorio original en GitHub antes de usarlo en producción.

¿Quién mantiene adityaarsharma/pickle?

+

adityaarsharma/pickle es mantenido por adityaarsharma. La última actividad registrada en GitHub es de today, con 0 issues abiertos.

¿Hay alternativas a pickle?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega pickle en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: adityaarsharma/pickle
[![Featured on ClaudeWave](https://claudewave.com/api/badge/adityaarsharma-pickle)](https://claudewave.com/repo/adityaarsharma-pickle)
<a href="https://claudewave.com/repo/adityaarsharma-pickle"><img src="https://claudewave.com/api/badge/adityaarsharma-pickle" alt="Featured on ClaudeWave: adityaarsharma/pickle" width="320" height="64" /></a>

Más MCP Servers

Alternativas a pickle