Skip to content

Releases: adityaarsharma/pickle

v1.1.0 β€” Hosted server source published for enterprise audit

17 May 18:00

Choose a tag to compare

Pickle's hosted MCP server, landing page, and welcome email template are now public for enterprise audit transparency. Runtime state (signups.json, usage.json, .env, node_modules) stays private.

What's now auditable in source

  • server-remote/server.mjs β€” the entire hosted MCP server (2,753 lines)
  • server-remote/public/index.html β€” full landing page
  • server-remote/public/legal/ β€” privacy, terms, refund pages
  • server-remote/public/admin.html β€” admin dashboard
  • server-remote/package.json β€” runtime dependencies

New since v1.0.0

  • 57 MCP tools live: 46 ClickUp + 1 pickle_setup + 5 Slack + 5 Microsoft Teams
  • Free vs Pro split: 9 free ClickUp patterns vs 4 cross-tool patterns that ship later
  • Install-prompt onboarding: signup β†’ email-delivered prompt β†’ AI installs Pickle into user's existing MCP config (alongside other servers, safe-harbour mode)
  • "Pickle Start" trigger for the chat-guided platform setup
  • Re-entrant pickle_setup that shows per-platform connection status
  • Smart "wrong platform" errors that list what the user IS connected to
  • Anonymous platforms_seen tracking per pickle key (no workspace data, just timestamps)
  • Welcome email v3.2 β€” branded, copy-paste install prompt, founder vision, no Pro upsell pushiness

Privacy properties (verifiable in source)

  • Stateless: platform tokens travel in HTTPS request headers, used in memory to call ClickUp/Slack/Teams APIs, then dropped. Nothing persisted server-side.
  • No workspace data, no chat content, no task bodies are ever written to disk
  • Same email β†’ same pickle key (no key churn on re-signup)
  • SSRF allowlist: api.clickup.com, slack.com, graph.microsoft.com, login.microsoftonline.com
  • Zero hardcoded credentials; all secrets come from process.env

Install

```

  1. Sign up at https://pickle.adityaarsharma.com (free, no card)
  2. Email arrives with a one-time install prompt + your unique Pickle key
  3. Paste the prompt into Claude Code / Cursor / Cline / Codex
  4. Your AI installs Pickle into its own MCP config (safe-harbour, doesn't touch other servers)
  5. Restart your assistant, type "Pickle Start" in a new chat
  6. Guided setup walks you through ClickUp / Slack / Microsoft Teams token capture
    ```

Links


Built by Aditya Sharma Β· MIT licensed

v1.0.0 β€” Pickle: hosted MCP audit for ClickUp, Slack & Microsoft Teams

17 May 17:10

Choose a tag to compare

Pickle is a hosted MCP server that audits ClickUp, Slack, and Microsoft Teams workspaces for 13 patterns a good ops manager would catch β€” stale tasks, broken promises, decisions lost in DMs, 40-hour empty descriptions, ghost mode, and more.

Highlights

  • Hosted MCP at https://pickle.adityaarsharma.com/mcp
  • Stateless by design: user tokens travel only in HTTPS request headers, never written to disk or logged. No workspace data ever lands on Pickle's server.
  • 57 MCP tools β€” 46 ClickUp + 1 setup wizard + 5 Slack + 5 Microsoft Teams
  • Free 7-day audit window cap. Pro tier (Manager Mode, deeper history, always-watching agent) is being designed with the Beta cohort.
  • Quality standards live in CLAUDE.md β€” read before editing.

Install (one-time)

  1. Sign up at https://pickle.adityaarsharma.com to get your Pickle key by email.
  2. Paste the MCP config block from the email into Claude / Cursor / Cline / Codex.
  3. Restart your assistant.
  4. In chat, ask: "Pickle, set me up for ClickUp" β€” Pickle walks you through the 30-second token setup.
  5. Same flow for Slack and Microsoft Teams.

Privacy & terms

Support

Email pickle@adityaarsharma.com β€” replies same-day from a real human.


Built by Aditya Sharma Β· MIT licensed