Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Stop copy-pasting between Claude Chat and Claude Code.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://your-herald-instance.example.com/mcpRun this in your terminal
claude mcp add --transport http herald https://your-herald-instance.example.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"herald": {
"url": "https://your-herald-instance.example.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"herald": {
"type": "http",
"url": "https://your-herald-instance.example.com/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://your-herald-instance.example.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account btouchard, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Herald
Code from your phone. Seriously.
The self-hosted MCP bridge between Claude Chat and Claude Code.
Documentation · Quick Start · How It Works · Features · Security · Roadmap
🇫🇷 Version française
You're on the couch. On your phone. You open Claude Chat and type:
*"Refactor the auth middleware in my-api to use JWT instead of session cookies. Run the tests."*
Four minutes later, it's done. Branch created, code refactored, tests passing, changes committed. Your workstation did all the work. You never opened your laptop.
That's Herald.
Claude Chat and Claude Code are two brilliant tools that live in completely separate worlds.
| Claude Chat | Claude Code | |
|---|---|---|
| Where | Browser, phone, anywhere | Your terminal |
| What | Conversations, analysis, thinking | Reads, writes, and ships actual code |
| Gap | Can't touch your codebase | Can't leave your desk |
You've been copy-pasting between them. Or worse — you've been waiting until you're back at your desk. That's over.
Herald is a self-hosted MCP server that bridges Claude Chat to Claude Code using Anthropic's official Custom Connectors protocol. One Go binary. Zero hacks.
You (phone/tablet/browser)
│ │ "Add rate limiting to the API" ▼ Claude Chat ──── MCP over HTTPS ────► Herald (your workstation) │ ▼ Claude Code ├── reads your codebase ├── writes the code ├── runs the tests └── commits to a branch
You (terminal) │ │ Claude Code calls herald_push ▼ Claude Code ──── MCP ────► Herald ────► Claude Chat picks it up └── session context, summary, files modified, git branch
The bridge is bidirectional. Claude Chat dispatches tasks to Claude Code, and Claude Code can push session context back to Herald for remote monitoring and continuation from another device.
Your code never leaves your machine. Herald just orchestrates.
You (Claude Chat) Herald Claude Code
───────────────── ────── ─────────── "Refactor auth..." ──► start_task → creates branch → spawns Claude Code ──► reads codebase refactors code runs tests commits changes ◄── task_id: herald-a1b2c3d4
"How's it going?" ──► check_task ◄── ✅ Completed (4m 12s) 4 files changed (+127/-23)
"Show me the diff" ──► get_diff ◄── auth/middleware.go +func ValidateJWT(...) -func CheckSession(...)
Three tools. That's the core loop. Start, check, get results — all from wherever you are.
Working in your terminal and want to continue from your phone? Claude Code pushes its session to Herald:
You (terminal) Claude Code Herald
────────────── ─────────── ────── "Push this to Herald" ──► herald_push → session_id, summary, files, branch ──► linked task created 🔗 visible in list_tasks
You (phone, later) Claude Chat Herald ────────────────── ─────────── ────── "What sessions are list_tasks waiting for me?" ──► (status: linked) ──► 🔗 herald-a1b2c3d4 my-api / feat/auth
"Resume that session" ──► start_task (session_id) ──► picks up where you left off
herald_push for remote monitoring and continuation from another device.Prerequisites: Claude Code CLI installed, HTTPS via ngrok (built-in) or a domain with reverse proxy.
1. Install
curl -fsSL https://raw.githubusercontent.com/btouchard/herald/main/install.sh | sh
Or build from source (requires Go 1.26+)
git clone https://github.com/btouchard/herald.git
cd herald && make build
</details>
2. Configure
mkdir -p ~/.config/herald
cp configs/herald.example.yaml ~/.config/herald/herald.yaml
3. Run
herald serve
Edit ~/.config/herald/herald.yaml with your domain and projects:
server:
host: "127.0.0.1" port: 8420 public_url: "https://herald.yourdomain.com"
auth: client_id: "herald-claude-chat"
projects: my-api: path: "/home/you/projects/my-api" description: "Main backend API" default: true allowed_tools:
Then connect from Claude Chat:
https://herald.yourdomain.com/mcpDon't have a domain or reverse proxy? Use ngrok to expose Herald instantly over HTTPS:
1. Get ngrok auth token
Sign up at ngrok.com (free plan works) and grab your auth token from the dashboard.
2. Enable tunnel in config
Edit ~/.config/herald/herald.yaml:
tunnel:
enabled: true provider: "ngrok" authtoken: "2abc..." # or set HERALD_NGROK_AUTHTOKEN env var
3. Run Herald
herald serve
Connect from Claude Chat using the ngrok URL shown in the banner. That's it — no Traefik, Caddy, or DNS setup required.
Note: The ngrok tunnel is optional. If you already have a reverse proxy (Traefik/Caddy), leave
tunnel.enabled: falseand use your domain as usual.
Full configuration reference
server:
host: "127.0.0.1" # Always localhost — reverse proxy handles external port: 8420 public_url: "https://herald.yourdomain.com" log_level: "info" # debug, info, warn, error log_file: "" # Optional file path for log output
auth: client_id: "herald-claude-chat"
access_token_ttl: 1h refresh_token_ttl: 720h # 30 days redirect_uris:
database: path: "~/.config/herald/herald.db" retention_days: 90
execution: claude_path: "claude" model: "claude-sonnet-4-5-20250929" # Default model for tasks default_timeout: 30m max_timeout: 2h work_dir: "~/.config/herald/work" max_concurrent: 3 max_prompt_size: 102400 # 100KB max_output_size: 1048576 # 1MB env: CLAUDE_CODE_ENTRYPOINT: "herald" CLAUDE_CODE_DISABLE_AUTO_UPDATE: "1"
projects: my-api: path: "/home/you/projects/my-api" description: "Main backend API" default: true allowed_tools:
tunnel: enabled: false # Set to true to enable ngrok tunnel provider: "ngrok" authtoken: "" # or set HERALD_NGROK_AUTHTOKEN env var
rate_limit: requests_per_minute: 200 burst: 100
Herald exposes 10 tools that Claude Chat discovers automatically via the MCP protocol:
| Tool | What it does |
|---|---|
start_task | Launch a Claude Code task. Returns an ID immediately. Supports priority, timeout, session resumption, and Git branch options. |
check_task | Check status and progress. Optionally include recent output. |
get_result | Get the full result of a completed task (summary, full, or json). |
list_tasks | List tasks with filters — status, project, time range. |
cancel_task | Cancel a running or queued task. Optionally revert Git changes. |
get_diff | Git diff for a task's branch or uncommitted changes. |
list_projects | List configured projects with Git status. |
read_file | Read a file from a project (path-safe — cannot escape project root). |
herald_push | Push a Claude Code session to Herald for remote monitoring and continuation from another device. |
get_logs | View logs and activity history. |
Herald expos
Only the beginning is shown; read the rest in the repo