Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Connect AI agents to Emitd email sending, message tracking, templates, and automations.
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.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http emitd https://mcp.emitd.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"emitd": {
"url": "https://mcp.emitd.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}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": {
"emitd": {
"type": "http",
"url": "https://mcp.emitd.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}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.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese 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 6, 2026
The registry name was verified against the domain emitd.com (the registry checks domain ownership)
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.
You need to fill in: Authorization
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.1) reached the registry 12 days 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.
Connect AI agents and MCP-compatible clients to Emitd's hosted email platform through the Model Context Protocol (MCP).
Authorization: Bearer Important: This repository documents and provides connection examples for Emitd's hosted MCP service. It does not contain the implementation of Emitd's hosted server.
https://mcp.emitd.com/mcp.Authorization: Bearer header through the client's supported secret configuration.The exact configuration fields vary by MCP client. Use this as a reference, not as a universal drop-in configuration:
{
"mcpServers": { "emitd": { "url": "https://mcp.emitd.com/mcp", "headers": { "Authorization": "Bearer ${EMITD_API_KEY}" } } } }
Some clients do not expand environment variables in remote HTTP headers. Use the client's supported secret-management UI when necessary. Never commit a real API key to source control.
Emitd's documented connection pattern:
claude mcp add --transport http emitd https://mcp.emitd.com/mcp \
--header "Authorization: Bearer YOUR_EMITD_API_KEY"
Replace the placeholder locally with your key. Avoid placing live credentials in shell history or shared terminal logs where possible.
Emitd's documentation describes capability areas including:
The exact tool names and availability may change and depend on the API key's permissions and enabled features. Consult the official guide for the current tool inventory. This repository does not guarantee that every capability is enabled for every account.
This is a documentation and configuration-example repository for a hosted service. Before relying on any configuration, check the current Emitd documentation and your MCP client's supported remote-server settings.
Please do not submit secrets, customer data, or sensitive email content in issues or pull requests.
MIT License. See LICENSE for details.