D
Dipeshpal/capes
Superpowers for any AI: a free, self-hosted MCP server (Gmail, Discord, X) with a dashboard. Deploy to your own Vercel in minutes.
SECURITY.md ✓
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
客户端配置（取自该仓库的安装命令）
{
"mcpServers": {
"dipeshpal-capes": {
"command": "uvx",
"args": ["ruff"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README；我们未执行过。
command/args 来自仓库写明的安装命令；不确定时请以该项目 README 为准。
VS Code（.vscode/mcp.json —— 键名是 servers）
{
"servers": {
"dipeshpal-capes": {
"command": "uvx",
"args": ["ruff"]
}
}
}VS Code 顶层键是 <code>servers</code>，其余与上面那份相同。
Claude Code（命令行）
claude mcp add --transport stdio dipeshpal-capes -- uvx ruff
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- ★ 数取值
- 1 ★ · Dipeshpal/capes · 取自 GitHub 搜索 API · （2026-11-13 20:00:50 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 1 ★ · 23 个来源 · mcp
- 安装
uvx ruff
常见问题（答案都来自我们的记录）
怎么安装？
该仓库给出的安装命令是
uvx ruff。我们的记录里它是仓库自己提供的；不保证在你的客户端上直接可用。它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
Dipeshpal/capes；我们收录于 2026-10-23；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。### Give Claude, Codex, Cursor and any MCP client hands: your Gmail, Discord and
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
🚀 Start
Quick start
Deploy
Connect a client
💡 Learn
What you get
A day with Capes
How it works
⚙️ Reference
Services
Dashboard
All 68 tools
💬 Community
What's built
What's next
Request a feature · ☕ Support
🤝 Project
Security
Contributing
Documentation
## 🎬 Demo
▶ Watch the demo on YouTube
Fresh Vercel deploy, checking connectors, browsing all 68 tools, connecting a client, and asking Claude to use it.
## ✨ What you get
AI assistants read, summarise and act well, but your real work lives in accounts they cannot reach. Capes is one private MCP server that you deploy to your own Vercel account. Connect it once and the same tools appear in every AI client you use.
| | What it does |
| 📧 Gmail (17 tools) | Search with Gmail syntax, read, send, reply, forward, drafts, labels, archive, trash. No Google Cloud project, just an app password. |
| 💬 Discord (47 tools) | Read and post, edit, delete, react, threads, forums, polls, files, webhooks, channels, roles, permissions, moderation, audit log. |
| 🐦 X / Twitter (1 tool) | Search tweets through an Apify scraper. |
| ✈️ Telegram (3 tools) | Send messages, get chat info, poll recent updates. |
| 🖥️ Dashboard | Test each service's credentials, browse and try the tools, watch recent activity, copy ready-made client config. |
| 🛡️ Limits you control | Turn a service or a single tool off, or make the whole server read-only. Tools are labelled read, write or destructive. |
| 🔑 You own it | Your credentials live only in your Vercel project and your own Postgres database. No central service, no account with us. |
## 🎬 A day with Capes
Sam runs a small product and its Discord community, and answers customers from one Gmail inbox. Every morning Sam asks one question in Claude:
> Sam: Give me a briefing. Unread customer emails from the last day, unanswered questions in #support, and what people are saying about our product on X.
The assistant, using tools from the same server:
1. gmailsearch for is:unread newerthan:1d, then gmailgetmessage on the ones that look like customers. It groups them: 3 billing questions, 1 bug report, 2 newsletters.
2. discordreadchannel on #support, and finds 4 questions nobody answered.
3. twittersearch for the product name, and summarizes the tone of 20 recent tweets.
> Sam: Draft replies to the billing emails, and answer the two easy Discord questions. Show me everything before you send.
4. gmailcreatedraft for each reply (drafts, nothing sent yet).
5. Shows Sam the drafts and the two Discord answers. Sam approves.
6. gmailsenddraft, discordsendmessage, and gmailmodify to label and archive the handled mail.
That is about five minutes instead of forty, and the assistant never had direct access to Sam's accounts: everything went through Sam's own server, with Sam's own limits. When Sam wants an assistant to only look, one switch in the dashboard hides every tool that sends or deletes.
This is an illustration of what the tools make possible, not a recording.
Why not just use each app's built-in connectors?
One setup for every client. The same server works in Claude Desktop, Claude Code, Cursor and Codex, not just one app.
You hold the credentials. They sit in your own Vercel project, not in a third-party platform.
Quick start
Deploy
Connect a client
💡 Learn
What you get
A day with Capes
How it works
⚙️ Reference
Services
Dashboard
All 68 tools
💬 Community
What's built
What's next
Request a feature · ☕ Support
🤝 Project
Security
Contributing
Documentation
## 🎬 Demo
▶ Watch the demo on YouTube
Fresh Vercel deploy, checking connectors, browsing all 68 tools, connecting a client, and asking Claude to use it.
## ✨ What you get
AI assistants read, summarise and act well, but your real work lives in accounts they cannot reach. Capes is one private MCP server that you deploy to your own Vercel account. Connect it once and the same tools appear in every AI client you use.
| | What it does |
| 📧 Gmail (17 tools) | Search with Gmail syntax, read, send, reply, forward, drafts, labels, archive, trash. No Google Cloud project, just an app password. |
| 💬 Discord (47 tools) | Read and post, edit, delete, react, threads, forums, polls, files, webhooks, channels, roles, permissions, moderation, audit log. |
| 🐦 X / Twitter (1 tool) | Search tweets through an Apify scraper. |
| ✈️ Telegram (3 tools) | Send messages, get chat info, poll recent updates. |
| 🖥️ Dashboard | Test each service's credentials, browse and try the tools, watch recent activity, copy ready-made client config. |
| 🛡️ Limits you control | Turn a service or a single tool off, or make the whole server read-only. Tools are labelled read, write or destructive. |
| 🔑 You own it | Your credentials live only in your Vercel project and your own Postgres database. No central service, no account with us. |
## 🎬 A day with Capes
Sam runs a small product and its Discord community, and answers customers from one Gmail inbox. Every morning Sam asks one question in Claude:
> Sam: Give me a briefing. Unread customer emails from the last day, unanswered questions in #support, and what people are saying about our product on X.
The assistant, using tools from the same server:
1. gmailsearch for is:unread newerthan:1d, then gmailgetmessage on the ones that look like customers. It groups them: 3 billing questions, 1 bug report, 2 newsletters.
2. discordreadchannel on #support, and finds 4 questions nobody answered.
3. twittersearch for the product name, and summarizes the tone of 20 recent tweets.
> Sam: Draft replies to the billing emails, and answer the two easy Discord questions. Show me everything before you send.
4. gmailcreatedraft for each reply (drafts, nothing sent yet).
5. Shows Sam the drafts and the two Discord answers. Sam approves.
6. gmailsenddraft, discordsendmessage, and gmailmodify to label and archive the handled mail.
That is about five minutes instead of forty, and the assistant never had direct access to Sam's accounts: everything went through Sam's own server, with Sam's own limits. When Sam wants an assistant to only look, one switch in the dashboard hides every tool that sends or deletes.
This is an illustration of what the tools make possible, not a recording.
Why not just use each app's built-in connectors?
One setup for every client. The same server works in Claude Desktop, Claude Code, Cursor and Codex, not just one app.
You hold the credentials. They sit in your own Vercel project, not in a third-party platform.
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/dipeshpal-capes/)
- 来源
- awesome · https://github.com/Dipeshpal/capes
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 该仓库根目录有
SECURITY.md（我们只核文件存在，未核内容）
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。