Vexa
de Vexa-ai
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Se ejecuta en la nube★ 2949Apache-2.0Actualizado hace 2 meses
Instalar
Hub
Resumen
Descripción del creador (original en inglés)
Multiple Google accounts (Gmail, Calendar, Drive, Contacts, Tasks) in one Claude connector.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en la nube
- Transporte: Streamable HTTP
- Categoría: Chat y correo
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en el servidor del creador: lo que le pidas pasa por su servidor.
- El registro no indica ninguna clave que completar.
Necesitas
- Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
- Abre Settings → Connectors
- Presiona Add custom connector
- Pega la dirección de abajo y presiona Add
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://hub.grounders.app/mcpEjecuta esto en tu terminal
claude mcp add --transport http hub https://hub.grounders.app/mcpO copia la configuración tú
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"hub": {
"url": "https://hub.grounders.app/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
O copia la configuración tú
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"hub": {
"type": "http",
"url": "https://hub.grounders.app/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
- Abre ChatGPT en la web → Settings → Connectors (Apps)
- Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
- Pega la dirección de abajo, ponle un nombre y guarda
- Si te pide iniciar sesión, inicia sesión en el servicio del creador
https://hub.grounders.app/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub ItsBreeze, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
El endpoint responde
Aún sin revisar; revisamos los endpoints por turnos
- … Aún sin revisar
Inicio de sesión con OAuth
Aún sin revisar; revisamos los endpoints por turnos
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint
Comparado con otros en Chat y correoi
- Más estrellas que el 0% de los otros 1772 servidores de esta categoría
- Publicado en el registro más recientemente que el 39% de los otros 1772 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 1772 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro Hub?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (1.1.0) llegó al registro hace 42 días.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
¿Qué puedo usar en su lugar?
En la misma categoría: Vexa, emailmd, MCP WhatsApp Cloud
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
emailmd
de anypost
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Computadora o nube★ 1385MITActualizado hace 31 días
Instalar
MCP WhatsApp Cloud
de codespar
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Se ejecuta en tu computadora★ 277MITActualizado hace 5 meses
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Hub — a multi-account Google connector for Claude
A remote MCP server that gives Claude access to several Google accounts at once — Gmail, Calendar, Drive, Contacts and Tasks. Claude's built-in Google connectors each hold exactly one account; connecting a second replaces the first. This holds as many as you link, and every search tool fans out across all of them in a single call.
AOL mailboxes link too. They are reached over IMAP and SMTP with an app password, sit behind the same mail tools, and are searched together with Gmail — see AOL mailboxes.
Run it yourself and it holds your Google tokens in your own database, encrypted, and talks to Google directly — nothing passes through a third party. Or try the hosted one first.
Node and Postgres, six tables. Dependencies are Express, pg and jsonwebtoken, plus imapflow, mailparser and nodemailer for AOL — IMAP, MIME and SMTP are protocols, not parsing jobs, and each library is the maintained standard for its one. Document text extraction — PDF, Word, Excel, PowerPoint, OpenDocument — uses only Node's standard library.
Status: running in production against real mailboxes, with 564 automated checks. Built for one person's needs and published because the one-account limit is not unique to them. Treat it as working software with a small user base, not as a hardened product.
Try the hosted one
A copy runs at hub.grounders.app. It is in testing, and free while it is.
- In Claude: Settings → Connectors → Add custom connector, with the URL
https://hub.grounders.app/mcp. ChatGPT, Cursor and other MCP clients take the same URL as a remote MCP server. - Sign in with Google once when asked.
- Link each account at hub.grounders.app/gmail/connect.
Google's review of the app is still in progress, so you will see an "unverified app" screen the first time.
Quick start
git clone https://github.com/ItsBreeze/google-multi-account-mcp.gitcd google-multi-account-mcp npm install cp .env.example .env # fill it in — see Setup below npm run migrate # creates the six tables npm start
Then deploy it somewhere with a public HTTPS URL (Railway, Fly, Render, a VPS — anything that runs Node and reaches Postgres) and follow Setup.
Endpoints
| Method | Path | Description |
|---|---|---|
| POST | /mcp | MCP Streamable HTTP endpoint (Bearer auth) |
| GET | /mcp/oauth/authorize | Consent screen — operator password |
| POST | /mcp/oauth/token | Token + refresh grants |
| POST | /mcp/oauth/register | RFC 7591 dynamic client registration |
| GET | /.well-known/oauth-protected-resource | RFC 9728 discovery |
| GET | /.well-known/oauth-authorization-server | RFC 8414 discovery |
| GET | /gmail/connect | Link an account (repeat per account) |
| GET/POST | /gmail/aol | Link an AOL mailbox with an app password (checked against AOL before it is stored) |
| POST | /gmail/unlink | Unlink one, revoking the grant at Google (or deleting the stored AOL app password) |
| GET/POST | /ai/k/ | Reply link for an AI agent without MCP: GET reads its thread, POST {"text"} answers |
Tools (59)
Every tool takes an optional account. On a search, omitting it fans the call out across every linked account and merges the results — the thing no single-account connector can do. On a write it names the one account to act on, so "create this event" is never ambiguous about whose calendar it lands in.
Mail — Gmail and AOL (23)
| Area | Tools | Notes |
|---|---|---|
| Accounts | list_accounts | Which accounts are linked, with token health |
| Search | search_messages, search_threads | Gmail query syntax, merged and date-sorted across accounts. search_threads returns one row per conversation — subject, every participant, message and unread counts, last activity — for "where does my thread with X stand" without pulling bodies |
| Read | get_message, get_thread, get_attachment | Bodies flattened to text and capped at 60 KB; attachment metadata included. `get_attachment` extracts text from PDF, Word, Excel, PowerPoint and OpenDocument attachments, so an emailed contract or invoice is readable directly; anything else comes back base64 (2 MB cap) |
| Send | send_message, reply_to_message, forward_message | Replies thread via In-Reply-To/References; forwards carry attachments (10 MB cap, skipped ones named); optional from + fromName send as a verified Gmail send-as alias |
| Drafts | create_draft, list_drafts, get_draft, update_draft, send_draft, delete_draft | create_draft with reply_to_message_id drafts an in-thread reply for review — the safe path for AI-written mail; create_draft and send_draft also take from/fromName (send_draft rewrites the draft's From first, Gmail only) |
| Labels | modify_labels, list_labels, create_label, update_label, delete_label | modify_labels takes message_id or thread_id; removing INBOX archives |
| Trash & spam | trash_message, untrash_message, mark_spam | All take message_id or thread_id; trash is recoverable for 30 days; mark_spam with unmark: true restores |
Calendar (9)
| Area | Tools | Notes |
|---|---|---|
| Read | list_calendars, list_events, search_events, get_event | list_events merges every linked calendar into one timeline, defaulting to the next 7 days; recurring series are expanded into actual occurrences, so a weekly standup appears on each day it happens |
| Write | create_event, update_event, delete_event | Times are ISO 8601; a bare YYYY-MM-DD means all-day. update_event patches — unmentioned fields keep their value. Attendees are not emailed unless send_updates says so |
| Repeats | create_event, update_event, delete_event | repeat: "weekly" (with repeat_count or repeat_until) covers the ordinary cases; recurrence takes full RFC 5545 rules. On a repeating event, scope chooses one occurrence or the whole series — see below |
| RSVP | respond_to_event | accepted / declined / tentative, as the account that was invited; notifies the organiser by default |
| Scheduling | suggest_time | Free slots across every linked calendar at once — busy anywhere means busy. Returns whole gaps rather than chopping a 3-hour opening into six half-hour slots |
Drive (15)
| Area | Tools | Notes |
|---|---|---|
| Find | search_files, list_recent_files, get_file_metadata, list_shared_drives | Text search over names and contents, with optional raw Drive query syntax in filter. Covers My Drive and every shared drive at once; drive_id narrows to one. Trashed files excluded unless you ask for them |
| Read | read_file_content, download_file_content | Docs, Sheets and Slides exported (Sheets as CSV); PDF, Word, Excel, PowerPoint and OpenDocument extracted to text; ocr: true routes scans and images through Google's own conversion; include_comments returns the comment threads. download_file_content takes export_as — turn a Doc into a PDF or docx, a Sheet into xlsx. Text caps at 60 KB, binaries at 2 MB base64 |
| Write | create_file, update_file, copy_file | Text via content, binary via content_base64. convert_to makes Drive convert the upload into an editable Doc, Sheet or Slides — or a folder. update_file renames, moves and describes; overwriting contents additionally needs replace_content: true. On a file you do not own it edits a private copy — see below |
| Comment | comment_on_file | Leave a comment on a draft, or reply to a thread — the review path that changes nothing in the document |
| Sharing | get_file_permissions, share_file, unshare_file | Shares with one named person at reader/commenter/writer. Domain-wide and public-link sharing are off unless DRIVE_ALLOW_PUBLIC_SHARING=true, and then still need confirm_public. `unshare_file` withdraws access — by person, by domain, or by removing the public link |
| Remove | trash_file, untrash_file | Trash and restore, within the 30-day window — see the scope note below |
Contacts (2) and Tasks (5)
| Area | Tools | Notes |
|---|---|---|
| Contacts | search_contacts, list_contacts | Read-only. Searches saved contacts and people the account has corresponded with, so "email Ann" resolves to an address instead of a guess |
| Tasks | list_task_lists, list_tasks, create_task, update_task, delete_task | list_id defaults to the account's first list. update_task with completed: true ticks a task off; false reopens it. Google Tasks has no trash, so delete_task is permanent |
AI agents (5)
AIs talk to each other through Hub instead of by email. Every message has a thread, a hop count and a read time, so nothing is lost to subject matching and a sender can see whether it was read.
| Area | Tools | Notes |
|---|---|---|
| Talk | ai_send, ai_inbox, ai_thread | ai_send with thread answers in place and to defaults to the other side. ai_inbox with wait_seconds (up to 50) holds until a reply arrives. Threads stop at hop 10 |
| Agents | ai_agents, ai_set_agent | An agent can be woken by email (one JSON object from a linked mailbox, subject template like Claude -> Lute (hop {hop})) or by webhook (POST {"text"}, headers stored encrypted). A failed wake keeps the message unread and tells the sender |
An agent without MCP needs no account: each wake carries a signed reply_url (30 days, one owner, one agent). POST {"text":"..."} to it to answer, GET it to read the thread, or POST {"new_thread":true,"to":"claude","text":"..."} to start a new conversation.
AOL mailboxes
Link one at /gmail/aol with the address and an app password generated at AOL Account Security — AOL has no OAuth for third-party mail clients outside an approved partner list, so this is the only door. The password is signed in to IMAP before it is stored (one app password covers IMAP and SMTP), so a typo is reported on the link page, not on Claude's first tool call. It is stored AES-256-GCM encrypted under TOKEN_ENC_KEY, like the Google tokens. Hosts come from a preset in code (imap_providers.js), never from the request.
Sending goes through a relay where SMTP is blocked. Railway blocks outbound SMTP below its Pro plan, so hub.grounders.app hands each AOL submission over HTTPS to a Cloudflare Worker (smtp-relay/) that speaks SMTP to smtp.aol.com:465. The Worker stores and logs nothing and reaches only preset hosts. It is used when SMTP_RELAY_URL and SMTP_RELAY_TOKEN are set; without them the server talks SMTP directly, as a self-hosted copy that can reach port 465 should. Gmail sending is unaffected — it goes through Google's API.
The 23 mail tools work on an AOL mailbox unchanged, and a search with no account covers Gmail and AOL in one merged, date-sorted result. What differs is IMAP itself, and the tools say so rather than pretend:
| Gmail | AOL over IMAP |
|---|---|
| Labels, several per message | Folders, one per message. UNREAD/STARRED are flags; INBOX, SPAM, TRASH and folder names move the message. A change that would need two folders is refused; IMPORTANT and categories do not exist |
| Ids are permanent | An id is folder + UID, so a move gives the message a new id — every moving call returns it as new_message_id. An id from a folder the server renumbered is refused as stale, never resolved to a different message |
| Gmail query syntax | Translated to IMAP SEARCH: from: to: cc: bcc: subject: is:unread/read/starred has:attachment newer_than: older_than: after: before: in: label: larger: smaller:, phrases, OR, -, parentheses. Anything el
Solo se muestra el principio; lee el resto en el repo