Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
제작자가 쓴 설명(영어 원문)
Free, local MCP server that audits ClickUp, Slack & Teams for work that slipped through.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
CLICKUP_API_KEY, SLACK_TOKEN, TEAMS_TOKEN비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"pickle": {
"command": "npx",
"args": [
"-y",
"pickle-mcp"
],
"env": {
"CLICKUP_API_KEY": "your-value",
"SLACK_TOKEN": "your-value",
"TEAMS_TOKEN": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add pickle --env CLICKUP_API_KEY=your-value --env SLACK_TOKEN=your-value --env TEAMS_TOKEN=your-value -- npx -y pickle-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"pickle": {
"command": "npx",
"args": [
"-y",
"pickle-mcp"
],
"env": {
"CLICKUP_API_KEY": "your-value",
"SLACK_TOKEN": "your-value",
"TEAMS_TOKEN": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"pickle": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pickle-mcp"
],
"env": {
"CLICKUP_API_KEY": "your-value",
"SLACK_TOKEN": "your-value",
"TEAMS_TOKEN": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 GitHub 계정 adityaarsharma 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: CLICKUP_API_KEY, SLACK_TOKEN, TEAMS_TOKEN
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.1.0)은 4개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Vexa, emailmd, MCP WhatsApp Cloud
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
| 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, and there is no analytics, no beacon, no phone-home.
Guided: it asks which tools you use, points you to where each token lives, and writes your MCP config for you.
curl -fsSL https://pickle.adityaarsharma.com/install.sh | bash
Or add it to your MCP client yourself (via npm):
{
"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. The only token you ever provide is your own platform token (e.g. ClickUppk_…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."*
docs/patterns.mdClaude 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 add /pickle-* slash commands as a convenience layer.
Pickle has no paid tier and never will. Instead:
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.
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.
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? The audit itself is read-only — it only reads and reports. Pickle *can* create a reminder, drop a comment, or make a task if you explicitly ask it to (for example "remind me about XYZ-184"), because the server also exposes write tools for that. If you want a hard, code-level guarantee that nothing can be written or deleted no matter what a model asks, set PICKLE_READONLY=1 in the env block — it blocks every mutating tool at the server. Details in docs/security.md. 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. That's the consulting I do.
Issues and PRs welcome: new patterns, new connectors (a GitHub audit for stale PRs is a great first one), better client configs.
MIT © Aditya Sharma