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 ✓
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"dipeshpal-capes": {
"command": "uvx",
"args": ["ruff"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"dipeshpal-capes": {
"command": "uvx",
"args": ["ruff"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio dipeshpal-capes -- uvx ruff
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 1 ★ · Dipeshpal/capes · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 1 ★ · 23 sources · mcp
- Install
uvx ruff
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx ruff. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Dipeshpal/capes；first catalogued 2026-10-23；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.### 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.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/dipeshpal-capes/)
- Source
- awesome · https://github.com/Dipeshpal/capes
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 23 independent sources
- added
- today
- Security policy
- the repository has
SECURITY.mdat its root (we checked that the file exists, not what it says)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.