Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
作者提供的说明(英文原文)
Turn GitHub pushes into plain-English client update emails. Map repos to clients and review digests.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://relay-vishnu.fly.dev/mcp在终端中运行这条命令
claude mcp add --transport http relay https://relay-vishnu.fly.dev/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"relay": {
"url": "https://relay-vishnu.fly.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"relay": {
"type": "http",
"url": "https://relay-vishnu.fly.dev/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://relay-vishnu.fly.dev/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 vishnumuthyalu 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 290 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于15天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有: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、图片和脚本已被移除。链接会离开本站。
Plain-English client updates from every GitHub push
Live at [relay-vishnu.fly.dev](https://relay-vishnu.fly.dev/dashboard). Install the GitHub App, then add https://relay-vishnu.fly.dev/mcp to your MCP client, find Relay in the MCP Registry, or install the extension from the VS Code Marketplace or Open VSX.
Relay is a GitHub App for freelancers and agencies. Install it on your repositories, map each one to a client, and every push to the main branch becomes a short, jargon-free email summary written by Claude. Clients confirm by email before anything is sent, and every digest has a one-click unsubscribe.
sequenceDiagram
participant Dev participant GitHub participant Web as Relay web participant Queue as Postgres (pg-boss) participant Worker as Relay worker participant Claude participant Resend participant Client
Dev->>GitHub: git push GitHub->>Web: POST /webhook/github (HMAC-signed, installation id) Web->>Web: verify signature, claim X-GitHub-Delivery alt duplicate, filtered, or client not confirmed Web-->>GitHub: 200 duplicate / filtered else new push for an active mapping Web->>Queue: enqueue process-push Web-->>GitHub: 202 accepted Queue->>Worker: job Worker->>Claude: summarize commits (structured output), unless over the monthly cap Claude-->>Worker: validated summary Worker->>Resend: digest email + List-Unsubscribe Resend-->>Client: digest end
CLAUDE_ENABLED kill switch./dashboard for people who don't use MCP.Prerequisites: Node.js 22.12+, Docker (for Postgres), a GitHub App, an Anthropic API key and a Resend API key.
git clone https://github.com/vishnumuthyalu/relay-extension.git
cd relay-extension npm install cp .env.example .env # fill in the values; see docs/github-app.md docker compose up -d db # Postgres on localhost:5432 (dev + test databases) npm run migrate npm run dev # web process on :3000 npm run dev:worker # worker process, in a second terminal
GitHub must reach your machine for webhooks and sign-in, so run a tunnel (ngrok http 3000) and use its URL as PUBLIC_URL and in the app settings.
Then:
PUBLIC_URL/install and install the app on a repository.PUBLIC_URL/dashboard and sign in with GitHub.node simulate-webhook.js.To run everything in containers instead: docker compose up --build.
One image, two processes (web, worker), one Postgres. The hosted instance runs on Fly.io (one web and one worker machine) with Supabase Postgres; migrations run as Fly's release command before each deploy. See docs/deploy.md. Tags drive releases: v* deploys the backend and updates the MCP Registry entry, and ext-v* publishes the VS Code extension.
All settings are environment variables; .env.example lists and explains each one. The web and worker processes refuse to start if a required value is missing.
| Variable | Required | Purpose |
|---|---|---|
DATABASE_URL | Yes | Postgres connection string |
PUBLIC_URL | Yes | Public base URL (webhooks, sign-in callback, email links) |
SESSION_SECRET | Yes | 32+ random characters; signs sessions and email links |
GITHUB_APP_SLUG, GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, GITHUB_WEBHOOK_SECRET | Yes | From the GitHub App |
ANTHROPIC_API_KEY | Unless CLAUDE_ENABLED=false | Claude API key |
RESEND_API_KEY, FROM_EMAIL | Yes | Email delivery (verify your sending domain in Resend) |
ANTHROPIC_MODEL | No | Default claude-haiku-4-5 |
DIGEST_MONTHLY_CAP | No | Claude-written digests per installation per month, default 100 |
CLAUDE_ENABLED | No | false sends plain digests for everyone |
GITHUB_APP_ID, GITHUB_APP_PRIVATE_KEY | No | Pull request context in summaries |
INTEGRATIONS_KEY | No | Encrypts ticket-tracker tokens; enables tracker connections |
The JSON API is described in spec/openapi.yaml and validated at runtime. It uses the session cookie from Sign in with GitHub.
| Method | Path | Purpose |
|---|---|---|
GET | /api/me | You and the installations you can manage |
GET | /api/installations/{id}/mappings | Client mappings with status (pending, active, unsubscribed) |
PUT | /api/installations/{id}/mappings/{owner}/{repo} | Create or update a mapping; sends the confirmation email |
DELETE | /api/installations/{id}/mappings/{owner}/{repo} | Stop digests for a repository |
POST | /api/installations/{id}/mappings/{owner}/{repo}/test | Send a sample digest to a confirmed client |
GET | /api/installations/{id}/digests | Digest history |
GET | /api/installations/{id}/usage | This month's usage against the cap |
Other routes: POST /webhook/github (GitHub App deliveries), /mcp (remote MCP), /oauth/* and /.well-known/* (OAuth for MCP clients), /dashboard, /auth/login, /auth/callback, POST /auth/logout, /install, /confirm, /unsubscribe, /privacy, /health, /ready.
Remote: add https://relay-vishnu.fly.dev/mcp to your MCP client (or https:// /mcp for your own deployment). For example:
claude mcp add --transport http relay https://relay-vishnu.fly.dev/mcp
Local, against your own database:
RELAY_INSTALLATION_ID=12345678 npm run mcp # stdio server for one installation
npm run mcp:inspect # open it in the MCP Inspector
Client setup is in docs/mcp.md, and the tool contract is in spec/mcp-tools.md.
Tests run against a real Postgres: each test file gets its own schema, so suites run in parallel. docker compose up -d db creates the relay_test database.
npm test
npm run lint npx @stoplight/spectral-cli lint spec/openapi.yaml --ruleset .spectral.yaml
CI runs the same steps on Node 22 and 24 with a Postgres service container, and fails if coverage drops (npm run test:coverage).
relay-extension/
├── server.js # Web process: webhooks, sign-in, API, email link pages ├── worker.js # Worker process: sends digests from the queue ├── lib/ │ ├── config.js # Env validation │ ├── db/ # Postgres pool, migrations runner, tenant-scoped queries │ ├── jobs/process-push.js # One delivery: caps, Claude or fallback, email, records │ ├── queue.js # pg-boss setup │ ├── service.js # Per-installation operations shared by API and MCP │ ├── pipeline.js # Summarize + email │ ├── claude.js # Claude structured outputs + schema validation │ ├── email.js # Email HTML, unsubscribe headers, Resend │ ├── links.js # Signed confirm/unsubscribe links │ ├── github.js # GitHub OAuth (Sign in with GitHub) │ ├── oauth/ # MCP authorization server: clients, tokens, JWT │ ├── context/ # Optional PR and ticket context for summaries │ ├── github-app.js # GitHub App JWT and installation tokens │ ├── crypto-box.js # AES-256-GCM for stored tracker tokens │ ├── html.js, csrf.js # Server-rendered pages and form protection │ ├── security.js # Webhook HMAC verification │ └── retry.js # Retry with backoff for Claude and Resend ├── routes/ # webhook, mcp, oauth, auth, dashboard, api, email links ├── migrations/ # Numbered SQL migrations ├── mcp/ # MCP server, tools, resources, stdio entrypoint ├── spec/ # OpenAPI, JSON Schemas, webhook and MCP contracts ├── tests/ # Jest suites + helpers (per-file Postgres schema) ├── extension/ # VS Code extension: registers the remote MCP server ├── server.json # MCP Registry entry ├── fly.toml # Fly.io deployment (web + worker, migrations on release) ├── docs/ # GitHub App, MCP, summaries, deployment, ADRs, sequence diagram ├── docker-compose.yml └── Dockerfile
httpOnly cookies with SameSite=Lax. The JSON API only accepts JSON bodies, which blocks cross-site form posts.PUBLIC_URL/mcp (RFC 8707). PKCE is mandatory, authorization codes are single-use, refresh tokens rotate, and both are stored only as hashes. The /mcp endpoint checks the Host header against DNS rebinding.MIT