Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
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://contexterai.com/mcpRun this in your terminal
claude mcp add --transport http contexter https://contexterai.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"contexter": {
"url": "https://contexterai.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": {
"contexter": {
"type": "http",
"url": "https://contexterai.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://contexterai.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 maaakso, 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 2 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.
Share one AI context across ChatGPT, Claude and Telegram.
Save what you worked out with one AI, continue it in another — and share the context with people in Telegram, who keep working on it in their own AI.
Contexter is a hosted remote MCP server. This repository is its public documentation: the connection details, the tool catalogue and what does and does not move between tools. The server itself is hosted and closed-source — there is nothing to install and no key to manage.
https://contexterai.com/mcpYou plan something in ChatGPT. You continue it in Claude. You discuss it in a Telegram group. Every hop, you re-explain the project — and the person you are working with cannot pick it up at all, because your history lives inside your account.
Contexter gives the project one context instead of one copy per tool. Both assistants read and write the same records. You can share that context with a person, and they continue it in whichever AI *they* use.
Nothing is imported automatically. Connecting an assistant does not hand Contexter your chat history. Only the records you explicitly save — or ask your assistant to save — end up in a context.
Add a custom connector pointing at https://contexterai.com/mcp. Claude discovers the OAuth endpoints on its own; you sign in through Telegram and approve access once.
Add Contexter as a connector with the same URL. Same OAuth flow.
Anything that speaks Streamable HTTP with OAuth 2.1 works the same way — point it at https://contexterai.com/mcp.
Full walkthroughs, including what travels between each pair of tools:
Once connected, you talk to your assistant normally. For example:
Create a context called "Kitchen renovation" in Contexter and put my measurement notes in it.
What is in my Dolomites hike context?
Save this comparison to the AI-bot context and share it with Anna.
Twenty-six tools in four groups. Write tools require a human decision — the client acts for a person, and irreversible steps (sharing, publishing to a room, deletion) are confirmed rather than assumed.
Reading (8) — list_contexts, get_context_card, get_context_feed, list_records, list_sources, get_artifact, get_file, read_image_content
Saving (7) — save_artifact, save_file, create_context, add_records_to_context, update_artifact, update_context, set_context_notifications
Sharing (5) — share_context, revoke_context_access, check_share_audience, deliver_to_chat, invite_room_to_context
Removing (6) — remove_record_from_context, delete_record, leave_context, restore_record, delete_context, restore_context
Scopes, response shapes and the reasoning behind each one: contexterai.com/developers.
Two assistants, one project. Research in ChatGPT, drafting in Claude. The plan lives in a context both reach, so neither one starts from an empty page.
Two people, two different AIs. You share the context, not a document export. The other person opens it from whatever assistant they already pay for.
A group chat that does not lose its decisions. Add the bot to a Telegram group. Messages from the people who opt in become records; the context built from the chat is shared with those same people, and each of them works on it in their own AI, outside the group.
Privacy policy · Security model in plain words · Terms · Subprocessors
Open an issue here, or message @ai_contexter_bot in Telegram. Questions and answers for people already using it: contexterai.com/help.