Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Manage cron jobs, machines and run history in your norc account from any AI chat.
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 norc https://mcp.norc.app/mcp --header 'Authorization: Bearer {api_key}'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"norc": {
"url": "https://mcp.norc.app/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}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": {
"norc": {
"type": "http",
"url": "https://mcp.norc.app/mcp",
"headers": {
"Authorization": "Bearer {api_key}"
}
}
}
}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.
The server asks you to sign in before it lists its tools.
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 norcapp, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 1248 ms (HTTP 401)
Needs a key or token that you copy and paste yourself
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 2 of 3 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 (0.3.2) reached the registry 5 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.
MCP server for connecting AI platforms (Claude, ChatGPT, etc.) to your norc account — manage cron jobs, machines, and run history from a chat.
https://mcp.norc.app/mcp with your key as the Bearer token (exact field depends on the client).npx).claude_desktop_config.json:~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json (Microsoft Store install: %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json)mcpServers (keep any servers already there) and use your own key (vault → Settings → API Keys): {
"mcpServers": { "norc": { "command": "npx", "args": ["-y", "norc-mcp"], "env": { "NORC_API_KEY": "norc_sk_..." } } } }
On Windows, `npx` is a `.cmd` script and may fail to launch directly; use `cmd` instead:
"command": "cmd",
"args": ["/c", "npx", "-y", "norc-mcp"]
4. Quit Claude Desktop completely and reopen it. Closing the window is not enough. norc's tools then appear in the tools menu.
Install the norc plugin, which adds slash commands and starts this server for you, or add it directly:
claude mcp add norc --env NORC_API_KEY=norc_sk_... -- npx -y norc-mcp
Use the same command / args / env block as the Claude Desktop config above. Without NORC_API_KEY (or --stdio) the server starts in HTTP mode instead, and a missing or malformed key in stdio mode exits with an error.
For clients that only support remote servers, use https://mcp.norc.app/mcp (Streamable HTTP, POST) with the header Authorization: Bearer norc_sk_.... It is the same code as this repo, deployed on Vercel; your key is forwarded to vault.norc.app and not stored.
list_jobs, create_job, update_job, delete_joblist_machines, rename_machine, delete_machinelist_runssync_jobs — declarative sync of your full job set (like norc gitops). Dry run by default; jobs not listed are deleted when apply is true. Needs the gitops sync feature enabled on your account.This server is a thin, stateless client — it holds no secrets and no database access of its own. It only forwards your API key to vault.norc.app (or $NORC_VAULT_URL). Run your own instance if you'd like:
pnpm install
pnpm build PORT=3000 node dist/server.js
Note: self-hosting this server does not mean self-hosting norc itself — it still talks to the hosted norc API.
docker run -p 3000:3000 norcapp/norc-mcp
Set NORC_VAULT_URL if you're pointing at a non-default vault instance:
docker run -p 3000:3000 -e NORC_VAULT_URL=https://vault.norc.app norcapp/norc-mcp
MIT