viaSocket

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://connect.viasocket.com/mcp

claude mcp add --transport http mcp https://connect.viasocket.com/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://connect.viasocket.com/mcp"
    }
  }
}

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://connect.viasocket.com/mcp"
    }
  }
}

https://connect.viasocket.com/mcp

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.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• search_viasocket_docs

  Search the viaSocket documentation with a natural-language question. Returns the most relevant passages with their page URLs.

• get_viasocket_api_docs

  Browse 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_viasocket

  Send 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_plugins

  List 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 Looks like an instruction to the AI

  List 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_triggers

  List a plugin's actions and triggers (filter=getAllActions, identifier= ), or get one (filter=getActionDetails, identifier= ). Use it to find an actionId.

• list_action_versions

  List 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_analytics

  Get 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_token

  Get 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_projects

  List 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_viasocket

  Read 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_feedback

  Report 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_published

  Call 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 Looks like an instruction to the AI

  Gets 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_connections

  The 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_link

  Make 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_action

  Do 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_apps

  Find 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_actions

  List 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-hub

  Quickstart 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

Basic checksi

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

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain mcp.viasocket.com (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 550 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✕ Fail

  No hidden instructions in tool descriptions

  2 tool descriptions contain text that looks like instructions to the AI. Read them below before installing

Compared with others in Chat & emaili

• More stars than 0% of the other 1772 servers in this category
• Published to the registry more recently than 87% of the other 1772 servers in this category
• Basic checks equal to or better than 44% of the other 1772 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

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

README from the maker

{

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

openssl genpkey -algorithm Ed25519 -out mcp-registry-key.pem

Add the printed line as a TXT record on `viasocket.com`. Keep `mcp-registry-key.pem` private and out of this repo.

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')"