Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Run scheduled LLM-written email digests from local files and feeds. Local-first MCP server.
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agentmailkit": {
"command": "uvx",
"args": [
"agentmailkit",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add agentmailkit -- uvx agentmailkit mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentmailkit": {
"command": "uvx",
"args": [
"agentmailkit",
"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": {
"agentmailkit": {
"type": "stdio",
"command": "uvx",
"args": [
"agentmailkit",
"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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 ariaxhan, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
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.
You are an AI coding agent reading this to decide whether to install agentmailkit and how to call it. Run this:
pip install 'agentmailkit[mcp]'
claude mcp add agentmailkit -- agentmailkit mcp
Gemini CLI: gemini extensions install https://github.com/ariaxhan/agentmailkit.
Then call list_jobs with no arguments: it returns the five example jobs that ship inside the wheel, so it works before any config exists. preview_job(job_id=..., model="echo") renders one to a local file with no API key. run_job(job_id=...) defaults to dry_run=true; only dry_run=false sends real email.
Full tool reference, argument names and the Codex config snippet: llms.txt.
Scheduled, LLM-written email digests that run on your machine, read your own files, and send from your own inbox.
Live samples, generated end to end. Nothing hand-written. Start there, it explains this faster than the README can.
pip install agentmailkit
agentmailkit run morning-brief --dry-run # five example jobs ship with it, so this works immediately agentmailkit quickstart # render all five to a local HTML gallery; never sends agentmailkit init # copy them into ./jobs to make them yours
MIT licensed. No account, no vendor, no cloud required.
An email is two files: a JSON job and a markdown prompt.
{
"id": "morning-brief", "schedule": "0 7 * * *", "sources": ["papers=arxiv:cs.AI#6", "weather=weather:Brooklyn"], "render": "warm", "delivery": "gmail", "dedup": true }
The engine runs one fixed pipeline and never grows a special case:
gather sources -> render prompt -> generate -> gate -> theme -> deliver -> post
ChatGPT Tasks, Claude Routines, Gemini Scheduled Actions and Copilot all execute in the vendor's cloud, which costs them two things:
~/notes, not a local database, not your git working tree.agentmailkit runs where your data already is. Nothing is uploaded except the prompt you choose to send to a model, and with a local model, not even that.
And it is deterministic. It is not an autonomous agent: it does not decide things, wander your filesystem, or act unrequested. The model writes the words; the engine owns everything else, so the same job produces the same shaped email every run. Local OSS agents can also read files and send mail, but they are broad autonomous systems you configure down to a task. This does one job, predictably, for years.
Full comparison including the honest counter-case: docs/comparison.md.
Hand your coding agent this link and it will set the whole thing up, asking you the right questions as it goes:
https://github.com/ariaxhan/agentmailkit/blob/main/AGENTS.md
AGENTS.md is a complete setup runbook: what to ask you, how to install, how to build your first job, how to verify before anything can send, and how to schedule it. CLAUDE.md is a symlink to the same file, so they can never drift apart.
agentmailkit speaks MCP, so your coding agent can drive it as a tool instead of you typing commands.
pip install 'agentmailkit[mcp]'
claude mcp add agentmailkit -- agentmailkit mcp
Codex, in ~/.codex/config.toml:
[mcp_servers.agentmailkit]
command = "agentmailkit" args = ["mcp"]
| Tool | What it does |
|---|---|
list_jobs | Every configured job with its schedule, sources and delivery target |
preview_job | Renders what one job would email, to a local file. Cannot send |
run_job | Runs one job. dry_run defaults to true |
list_plugins | Every registered source, model, gate, delivery backend and theme |
Or in Docker, with your jobs on a mounted volume: docker run -i --rm -v /path/to/jobs:/data mcp/agentmailkit.
Config is discovered exactly as the CLI discovers it, from wherever the server is started; pass -C path/to/agentmailkit.json in the args to pin one.
`run_job` with `dry_run=false` sends real email from your configured inbox. Every other tool, and the default dry_run=true, stops before delivery.
Needs Python 3.10 or newer, which is the MCP SDK's floor, not agentmailkit's.
| Job | Pulls | Interesting because |
|---|---|---|
morning-brief | weather, three news outlets, on-this-day | Outlets stay labelled, so the model can contrast their framing |
curiosity | archaeology and astronomy feeds, history | No work content at all, on purpose |
research-digest | Hugging Face, arXiv | Real ids, counts and links the model cannot invent |
repo-pulse | git log, diffstat, TODO markers | Reads your working tree, which no cloud scheduler can |
daily-brief | local files, git log | The minimal shape to copy |
Ten sources built in: file, glob, recent, shell, hf, arxiv, rss, news, history, weather. Anything with a feed or an API joins them in about thirty lines.
Ideas worth stealing: your city's council agendas, security advisories for your exact dependency list, exchange rates, a friend's blog, release notes for the tools you use, tide tables, ISS pass times over your house.
Nothing repeats. A seen-ledger strips already-sent items before the model ever sees them, so day two is not a reprint of day one.
| Quickstart | Five minutes to a real email |
| Setup guide for agents | Hand this to your coding agent |
| Sources | All ten, with arguments and examples |
| Jobs and prompts | Every job field, prompt conventions |
| Themes | The renderer, palettes, enforced house style |
| Dedup | The seen-ledger contract |
| Delivery and config | Gmail, SMTP, gates, configuration |
| Models | Backends, and why they are text-only |
| Scheduling | cron, launchd, systemd, CI, and the cloud tradeoff |
| Taper pieces | The optional computational-poetry companion |
| Plugins | Write a source in about thirty lines |
| Comparison | Versus cloud schedulers and local agents, honestly |
pip install agentmailkit # core, standard library only
pip install agentmailkit[gmail] # + Gmail delivery pip install agentmailkit[all] # + Anthropic and OpenAI backends pip install agentmailkit[mcp] # + the MCP server, to drive it from a coding agent
The core has zero required dependencies. Backends pull their own libraries only when enabled.
Published on PyPI: pypi.org/project/agentmailkit. Requires Python 3.9 or newer.
Alpha (0.2.2, on PyPI). Engine, plugins, dedup, themes, delivery and scheduler emitters all work and are exercised end to end against live APIs. quickstart renders a full sample set from your own data on first run, with no keys and no network round-trip, and cannot send by construction.
Known rough edges: the five shipped jobs carry example defaults (weather:Brooklyn, a fixed news trio) that you are expected to edit after agentmailkit init.
Issues and pull requests welcome. The rule that governs review: behaviour is configuration, not code. If a change adds an if to the engine for one email's sake, it probably wants to be a plugin.
MIT. See LICENSE.