Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Descripción del creador (original en inglés)
Use your apps from your AI: Gmail, Slack, Google Sheets, HubSpot and 2,300+ more on your accounts.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿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:
https://connect.viasocket.com/mcpEjecuta esto en tu terminal
claude mcp add --transport http mcp https://connect.viasocket.com/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://connect.viasocket.com/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ú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"mcp": {
"type": "http",
"url": "https://connect.viasocket.com/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:
https://connect.viasocket.com/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.
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
search_viasocket_docsSearch the viaSocket documentation with a natural-language question. Returns the most relevant passages with their page URLs.
get_viasocket_api_docsBrowse the viaSocket API docs, one level at a time. Call it without arguments to get the top level: the modules and pages with a short description and the endpoints they hold. Call it with `path` set to a module's or page's link (or path) to get what is inside it; each listing li
call_any_api_of_viasocketSend a POST, PUT, PATCH or DELETE request to any viaSocket API endpoint for the user and return its response: every write (create, update, publish, delete). For GET requests use call_any_read_api_of_viasocket. Look the endpoint up with get_viasocket_api_docs first to get its URL,
list_pluginsList every viaSocket Developer Hub plugin (app) the user's organization owns. Send filter=getAllPlugins and identifier equal to the orgId in the path. Start here to find a pluginId (rowid).
list_auth_versions Parece una instrucción para la IAList a plugin's authentication versions (filter=getAuthDetails, identifier= ) to find an authid. Responses include decrypted client secrets: never show them to the user.
list_actions_and_triggersList a plugin's actions and triggers (filter=getAllActions, identifier= ), or get one (filter=getActionDetails, identifier= ). Use it to find an actionId.
list_action_versionsList all versions of an action or trigger (filter=getActionVersions, identifier= ), with code, inputs, authid, status and verification status. Use fields to keep the response small.
get_plugin_analyticsGet run counts, error counts and flow counts for every action and trigger version of a plugin (filter=getPluginDetails, identifier= , optional startTime and endTime dates).
get_org_details_by_tokenGet the viaSocket organization (id and details) that the signed-in user's token belongs to. Read-only, no inputs. Call this first whenever you need the organization id (orgId) for other viaSocket Developer Hub calls such as List Plugins, Get Plugin or analytics, instead of asking
list_embed_projectsList an organization's embed projects (type=embed) for viaSocket SDK setup. Each data.projects[].id is a project_id (VIASOCKET_PROJECT_ID). Reuse an existing embed: one embed serves a whole product. Only if there is none, create one with the Create Embed Project endpoint (via cal
call_any_read_api_of_viasocketRead from any viaSocket API endpoint with a GET request for the user and return its response. Use it once you know the exact endpoint: look it up with get_viasocket_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server
report_feedbackReport a problem to viaSocket while building with it: an error, a confusion, wrong docs or skills, a user correction, or a missing capability. Problems only, never success; no need to ask the user; a failed report never stops the task. Plugs: fix or extend the user's own plugs (t
report_publishedCall once right after you publish something on the user's own plug (one in list_plugins): a new plug, or a new action, trigger, version or connection on it. viaSocket then reviews the published plug and may add missing actions or triggers. Body: pluginId (the plug rowid, required
get_viasocket_embed_secret Parece una instrucción para la IAGets the viaSocket organization's embed signing secret (VIASOCKET_EMBED_SECRET) into the developer's .env encrypted, so you never see it. Use it in SDK setup. Get orgId with get_org_details_by_token first. Before calling, run `docstar-cli key request` in the project folder and pa
list_connectionsThe app accounts the signed-in user has already connected to viaSocket. Body {} answers rows with auth_id, service_id, service_name and connection_label (a JSON string: parse it before showing it, e.g. the email of the Gmail account). Match service_id to find the auth_id an actio
create_connection_linkMake a sign-in link so the user connects an app account (Google, Slack, an API key…) to viaSocket. Body { "service_ids": [" "] } answers data[] with a connection_url per app. Give the user the link, wait until they say they signed in, then call list_connections again to get the a
run_app_actionDo one thing in the user's app right now, on their own account: send an email, post a message, add a row, create a record, fetch data. Body { service_id, action_id, auth_id, instructions, thread_id }: service_id from search_apps, action_id from list_app_actions, auth_id from list
search_appsFind an app the user wants to use from their AI: Gmail, Slack, Google Sheets, HubSpot, Notion, Trello or any of 2,300+ apps. Body { "searchquery": "gmail" } answers services[] with service_id, service_name and service_description. This is the first step whenever the user asks to
list_app_actionsList what an app can do for the user. Body { "serviceId": " " } (camelCase) answers actions[] with action_id, action_name, action_description and fields_for_action_details. Use it to pick the action that matches the request (Gmail "Send Email", Google Sheets "Add Row", HubSpot "C
quickstart-viasocket-developer-hubQuickstart for viaSocket: use the user's own apps from their AI (send an email, post to Slack, add a sheet row, read a CRM; any of 2,300+ apps), build automations (flows) across those apps, and for developers: build and manage viaSocket plugins in the Developer Hub, set up a prod
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con el dominio mcp.viasocket.com (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 550 ms (HTTP 200)
No hace falta iniciar sesión
2 descripciones de herramientas contienen texto que parece dar instrucciones a la IA. Léelas abajo antes de instalar
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.
Superó 2 de 3 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.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
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.
El repo de GitHub cambió por última vez –, y la última versión (1.1.0) llegó al registro hace 3 días.
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.
En la misma categoría: Vexa, emailmd, MCP WhatsApp Cloud
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
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
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.
Lets AI assistants use your apps through viaSocket: send an email, post to Slack, add a sheet row, read a CRM, on your own Gmail, Slack, Google Sheets, HubSpot or any of 2,300+ apps; automate across them; build and manage your plugins (apps) in the Developer Hub; and connect your product to other apps with the viaSocket SDK.
This is a remote MCP server (Streamable HTTP) at https://connect.viasocket.com/mcp. Nothing to install: your AI tool connects to it, and you sign in to viaSocket once through OAuth (the same account as viasocket.com). The docs tools work without signing in.
| Area | Tools |
|---|---|
| Docs | search_viasocket_docs, get_viasocket_api_docs, quickstart-viasocket-developer-hub |
| Your apps | search_apps, list_app_actions, list_connections, create_connection_link, run_app_action |
| Plugins (Developer Hub) | list_plugins, list_auth_versions, list_actions_and_triggers, list_action_versions, get_plugin_analytics, report_published |
| Account and SDK | get_org_details_by_token, list_embed_projects, get_viasocket_embed_secret |
| Any viaSocket API | call_any_read_api_of_viasocket (GET), call_any_api_of_viasocket (POST, PUT, PATCH, DELETE) |
| Feedback | report_feedback |
Using your apps (the connector): the guide for AI assistants is https://viasocket.com/docs/skill.md.
Install it from the Cline MCP Marketplace, or open MCP Servers → Configure MCP Servers and add this to cline_mcp_settings.json:
{
"mcpServers": { "viasocket": { "type": "streamableHttp", "url": "https://connect.viasocket.com/mcp", "disabled": false, "autoApprove": [] } } }
Then use the sign-in button next to `viasocket` in the MCP Servers list and sign in to viaSocket in the browser. Agent-driven install steps are in [llms-install.md](llms-install.md).
claude mcp add --transport http viasocket https://connect.viasocket.com/mcp
then run /mcp and sign in.
server.json is the listing for the official MCP Registry, as com.viasocket.mcp/mcp. The com.viasocket.mcp name is proven by owning the viasocket.com domain (a viasocket.com DNS login covers its subdomains too).
One-time setup: create a signing key and publish its public half on viasocket.com (Git Bash or any shell with OpenSSL):
openssl genpkey -algorithm Ed25519 -out mcp-registry-key.pem
echo "v=MCPv1; k=ed25519; p=$(openssl pkey -in mcp-registry-key.pem -pubout -outform DER | tail -c 32 | base64)"
Add the printed line as a TXT record on `viasocket.com`. Keep `mcp-registry-key.pem` private and out of this repo.
Publish (bump version first for any later change):
mcp-publisher login dns --domain viasocket.com --private-key "$(openssl pkey -in mcp-registry-key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"
mcp-publisher publish