Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Visual email & layout builder that turns AI assistants into a Temway authoring studio.
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 temway https://mcp.temway.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": {
"temway": {
"url": "https://mcp.temway.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": {
"temway": {
"type": "http",
"url": "https://mcp.temway.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 with the GitHub account temway, 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.
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.0) reached the registry 4 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.
Let your AI assistant design beautiful emails & layouts — in your Temway workspace.
A Model Context Protocol server that turns Claude, ChatGPT, Cursor and friends into a visual email & layout authoring studio.
Getting Started · Clients · Tools · Temway
Temway is a visual builder for emails and layouts. This MCP server exposes your Temway workspace to any MCP-compatible AI client: the model reads your brand tokens, drafts a promo / newsletter / welcome email, previews it, publishes it, and even sends a test — all through natural language. No code, no drag-and-drop, no copy-pasting HTML.
It is a hosted remote MCP server. You point your client at a URL with an API key (or OAuth for web clients) — there is nothing to install, build, or run locally. The server speaks the MCP Streamable HTTP transport.
🔒 No source here? Correct. This is the public onboarding repo for the
Temway MCP server. The server is operated by Temway and runs at
https://mcp.temway.com/mcp. This repo holds client configuration, tool
reference, and connectivity helpers. Report issues / request tools in
Your AI client (Claude / ChatGPT / Cursor / Desktop)
└─ MCP over HTTPS → https://mcp.temway.com/mcp Authorization: Bearer tmw_live_… ← API key (or OAuth token for web connectors) └─ Temway public API → your workspace
The model authenticates per-request, then drives your workspace through brand-aware templates, block mutations, layout artwork, live previews, and publishing.
API keys are minted by a team admin in the Temway dashboard. The key:
tmw_live_…emails:read, emails:write, layouts:read, layouts:write) that gate which tools succeedStore it securely — it's shown once.
The endpoint and a ready-to-paste config for each client are in examples/. The short version:
# Claude Code
claude mcp add --transport http temway https://mcp.temway.com/mcp \ --header "Authorization: Bearer tmw_live_xxxxxxxxxxxxxxxx"
That's it. The workspace is derived from the key.
*"Create a promo email for our summer sale, 25% off, brand colors, a big CTA
button, preview it, then publish it."*
The model will get_branding → create_email → apply_template → update_block → preview_email_web → publish_email for you.
The Temway server speaks the Streamable HTTP transport. Pick your client:
| Client | Config | File |
|---|---|---|
| Claude Code | claude mcp add --transport http … | examples/claude-code.md |
| Claude Desktop | mcpServers JSON | examples/claude-desktop.json |
| claude.ai (web) | OAuth connector URL | examples/claude-ai-web.md |
| ChatGPT | OAuth connector URL | examples/chatgpt.md |
| Cursor | MCP settings | examples/cursor.md |
| Any MCP client | Streamable HTTP URL | examples/generic.json |
Two credential types — both resolve onto the same workspace context:
Authorization: Bearer tmw_live_…. The workspace is derived from the key. Scope-bound.https://mcp.temway.com/mcp.The server exposes 58 tools across five groups. Reads need a *:read scope; mutations need *:write.
Discovery & context — brand tokens, schemas, catalogs
| Tool | What it does |
|---|---|
get_branding | Fetch workspace brand tokens (colors, fonts, logo, socials, footer). |
list_block_types / get_block_schema | Email block catalog + per-block editable fields. |
list_layout_element_types / get_element_schema | Layout element catalog + fields. |
get_universal_schema | Global email style fields. |
list_templates | Curated email starter templates. |
list_fonts | Usable fonts (web-safe for emails; + Google/custom for layouts). |
list_concepts / get_concept | Mental-model concept docs (read before authoring). |
list_layout_templates | Curated layout artwork starters. |
list_shape_presets / list_style_presets | Decorative SVG library + style keys. |
Emails — author, mutate, preview, publish, send
| Tool | What it does |
|---|---|
list_emails / get_email | Browse & read published/draft emails. |
create_email / update_email / delete_email / duplicate_email | CRUD. |
create_email_from_layout | Seed an email from a published layout. |
set_content / validate_content | Replace whole content / validate before saving. |
add_block / update_block / remove_block / move_block | Incremental block edits. |
set_universal | Merge global email styles. |
apply_template | Apply a brand-aware starter template. |
preview_email_web | Fast web-target preview (preferred while iterating). |
preview_email_html | Inbox-target MJML HTML (slower; verifies client rendering). |
publish_email | Render + store; marks the email published. |
test_send_email | Send a one-off test copy to an address. |
Layouts — free-form pixel-perfect artwork canvas
| Tool | What it does |
|---|---|
list_layouts / get_layout | Browse & read layouts. |
create_layout / update_layout / delete_layout / duplicate_layout | CRUD. |
set_layout_content | Replace the whole layout descriptor. |
add_layout_element / update_layout_element / remove_layout_element | Element edits (absolute positioning). |
add_custom_shape / add_shape_preset | Bespoke SVG or curated decorative shapes. |
apply_layout_template | Apply a layout starter (hero-banner, promo-card, …). |
fit_canvas_to_content | Tighten canvas bounds to visible elements. |
publish_layout | Snapshot for embedding in emails. |
Note: layouts rasterize to a single PNG when embedded in an email (text
not selectable). Author readable/clickable content as email blocks instead.
Concurrency locks — prevent clobbering on shared resources
acquire_* / get_*_lock_status / refresh_*_lock / release_*_lock / force_release_*_lock for both email and layout resources.
Block/element mutations are not atomic — never fire two on the same resource in parallel. Acquire the edit-lock first on shared resources.
Search & fetch
| Tool | What it does |
|---|---|
search | Search the workspace for emails/layouts by name/subject/tags. |
fetch | Fetch the full content of a search result by id. |
get_branding
→ create_email { name: "Spring sale" } → apply_template { template: "promo" } # brand-aware starter → update_block / add_block # tweak copy, CTA, colors → preview_email_web # fast preview (preferred) → publish_email # renders + marks published → test_send_email { to: "me@example.com" } # optional real send
The hosted endpoint is fully managed — most users never touch env vars. They only matter if you self-host or run the stdio transport.
| Var | Purpose | Required? |
|---|---|---|
TEMWAY_API_URL | Temway API base URL. | Only when self-hosting. |
TEMWAY_API_KEY | tmw_live_… key (stdio transport). | stdio only. |
TEMWAY_WORKSPACE_ID | Workspace id (stdio transport; HTTP derives from key). | stdio only. |
LOG_LEVEL | pino log level (default info). | no |
Verify the endpoint is reachable from your network before wiring up a client:
node scripts/healthcheck.mjs
(npx temway-mcp-healthcheck once published, or npm run healthcheck.)
This repo does not contain server source. If you need to run the server yourself (on-prem, air-gapped, custom auth), contact hi@temway.com or open an issue.
Is this open source?
The server is operated by Temway (source currently private). This repo is the public integration surface: client configs, tool reference, and helpers, published under the MIT license so you can copy configs freely.
Do I need to install Node / npm / anything?
No. The hosted remote transport means your client connects over HTTPS by URL — nothing runs locally. The optional healthcheck.mjs needs Node ≥ 18.17.
Which client should I use?
For local/CLI work: Claude Code or Cursor. For no-install browser use: claude.ai or ChatGPT with the OAuth connector. All configs are in examples/.
How are my emails protected from the model?
Credentials are scope-bound per key (*:read / *:write). Reads never mutate; every mutation is explicit. Narrow scopes to a read-only key for safe browsing.
MIT © Temway