Skip to main content
Glama

Server Details

ViaSocket is integration and AI infrastructure for developers. Connect 2,300+ apps, build and manage automated workflows, embed AI agents with persistent memory, and add authentication, organisations, and embedded integration UIs to your product through a single MCP server.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 21 tools

Disambiguation4/5

Most tools have clearly distinct purposes: search_apps, list_app_actions, list_connections, and run_app_action form a clear app-workflow chain, while the read/write API helpers are explicitly split by HTTP method. The only mild overlaps are get_viasocket_api_docs vs search_viasocket_docs (browse vs search) and the cluster of list_* tools (list_actions_and_triggers, list_action_versions, list_app_actions, list_auth_versions), which are distinguishable but require careful reading.

Naming Consistency4/5

The set mostly follows a snake_case verb_noun convention (list_plugins, get_org_details_by_token, create_connection_link, search_apps). Deviations are minor: the skill tool uses hyphens (quickstart-viasocket-developer-hub) and a few names are verbose (call_any_read_api_of_viasocket), but overall the pattern is predictable.

Tool Count3/5

At 21 tools this is on the heavy side, though the server genuinely spans several sub-domains (app actions, plugin development, embed SDK, docs, feedback). Each tool maps to a real capability, but the surface is large enough that an agent must lean on the quickstart skill to navigate it, so it sits at the borderline.

Completeness4/5

Coverage across the inferred domain is broad: app discovery, action listing, connections, action execution, plugin/version/auth management, embed project listing, docs lookup, and feedback reporting are all present. Minor gaps exist (e.g. no dedicated tool to create embed projects or manage connection deletion, handled via the generic API call), but these are workable.

Available Tools

21 tools
call_any_api_of_viasocketA
Destructive
Inspect

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, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-viasocket-developer-hub skill first: it explains which tool to use when. Pass the full url with path variables filled in, the headers the docs list, query params in query (not in the url) and the JSON body in body. For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Only for the viaSocket endpoints documented on this server: it attaches the viaSocket sign-in, so never use it for Embarko (ship.embarko.ai) or any other service. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.

Inputs: url (required), method (required), headers (required), body, +1 more.

call_any_read_api_of_viasocketA
Read-onlyIdempotent
Inspect

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 already gives them exactly. Load the quickstart-viasocket skill first: it explains which tool to use when. For POST, PUT, PATCH and DELETE use call_any_api_of_viasocket. Pass the full url with path variables filled in, the headers the docs list, and query params in query (not in the url). For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.

Inputs: url (required), headers (required), query.

get_org_details_by_tokenA
Read-onlyIdempotent
Inspect

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 the user for it.

Inputs: no named parameters.

get_plugin_analyticsA
Read-onlyIdempotent
Inspect

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).

Inputs: orgId (required), filter, endTime, startTime, +1 more.

get_request_statusA
Read-onlyIdempotent
Inspect

Check a request you filed with report_feedback, by the requestId it returned. Use it for a missing app, action, trigger or field (kind missing_capability) you left unwired with a VIASOCKET-PENDING comment: call it when you come back to that work, at most once an hour, never in a loop. Body { "requestId": "row..." }; the org comes from the sign-in. Answers status, message and next (what to do now): received or building (keep it unwired, check later); completed (it is public: call list_app_actions with its serviceId, no need to search for it, use its actionIds, wire the pending part and test it); waiting_for_connection (viaSocket built it but could not connect it with its own account, so it is published privately in your organisation: call create_connection_link with its serviceId, give the link to the person you work for, and once they have connected wire and test it as for completed); needs_human (a person at viaSocket is handling it; message says what is needed; tell the person you work for); not_possible (message says why; leave it unwired and tell them). success false with 'No request with this requestId' means the id is wrong or belongs to another organisation.

Inputs: requestId.

get_viasocket_api_docsA
Read-onlyIdempotent
Inspect

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 links the next level. Call it with path set to an endpoint's link ending in ".openapi.yml" to get that endpoint as an OpenAPI file: method, url, headers, query params, path variables, a request body example and sample responses. Fetch only the level you need.

Inputs: path.

get_viasocket_embed_secretAInspect

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 pass its publicKey; then run the save command this tool returns, then its emit command (the developer can choose another .env file). Never ask for, print or repeat the secret.

Inputs: orgId (required), publicKey (required).

list_actions_and_triggersA
Read-onlyIdempotent
Inspect

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

Inputs: orgId (required), fields, filter, identifier.

list_action_versionsA
Read-onlyIdempotent
Inspect

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.

Inputs: orgId (required), fields, filter, identifier.

list_app_actionsA
Read-onlyIdempotent
Inspect

List what an app can do for the user. Body { "serviceId": "<service_id from search_apps>" } (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 "Create Contact") before connecting or running anything. Public catalog, no sign-in needed.

Inputs: serviceId.

list_auth_versionsA
Read-onlyIdempotent
Inspect

List a plugin's authentication versions (filter=getAuthDetails, identifier=) to find an authid. Responses include decrypted client secrets: never show them to the user.

Inputs: orgId (required), fields, filter, identifier.

list_connectionsA
Read-onlyIdempotent
Inspect

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 action or automation needs; if the user has several accounts of one app, ask which. If the app is not there, use create_connection_link.

Inputs: no named parameters.

list_embed_projectsA
Read-onlyIdempotent
Inspect

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 call_any_api) after the developer confirms.

Inputs: orgId (required), type, bringflows.

list_pluginsA
Read-onlyIdempotent
Inspect

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).

Inputs: orgId (required), fields, filter, identifier.

quickstart-viasocket-developer-hubA
Read-only
Inspect

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 product's viaSocket keys, give a product its own MCP server. Routes plug work through the plug skills index, product integration through the viaSocket skill, and Embarko deploy through Embarko's quickstart. Load this before any viaSocket task. Call this to load the full instructions for this skill before doing the task.

Inputs: no named parameters.

report_feedbackAInspect

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 (the ones in list_plugins) yourself, and build a plug for an app that has none. A plug used in flows but not in list_plugins is viaSocket's: never edit it, report it here (refs.pluginId, refs.actionId; a missing action, trigger or field is kind missing_capability, with exactly what is needed and why). Body: source (sdk | http_api | plug | action | trigger | connection | skill | other), kind (error | confusion | missing_capability | wrong_instructions | user_correction) and feedback (what happened, in plain words), plus optional severity, stage, intent, attempted, expected, actual, error, refs, env and retries. Never include secrets, tokens or script_id. The org and user come from the sign-in. It answers { success, requestId, status, message }: for a missing capability keep the requestId next to the unwired part and check it later with get_request_status.

Inputs: env, kind, refs, error, +9 more.

report_publishedAInspect

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), published (new_plug | new_action | new_trigger | new_version | connection), plus optional app (the app's name), actionIds (rowids of the actions or triggers just published) and note (plain words, never secrets). No need to ask the user; a failed call never stops the task. The org and user come from the sign-in. Not for problems: use report_feedback for those.

Inputs: app, note, pluginId, actionIds, +1 more.

run_app_actionA
Destructive
Inspect

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_connections, instructions in plain words carrying every value (recipient, subject, body, sheet name…), thread_id an id you make up and reuse for retries of the same request. viaSocket's builder turns the instructions into the action's input and runs it; the reply is the app's own result. It acts for real, so say exactly what it will do (which account, which action, which values) and get the user's yes first. For something that should happen repeatedly ("every time", "every morning"), build an automation instead, as the skill describes.

Inputs: auth_id, action_id, thread_id, service_id, +1 more.

search_appsA
Read-onlyIdempotent
Inspect

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 send, read, create, update or search something in one of their apps, or to automate something across apps. The catalog is public: no sign-in needed for this call.

Inputs: searchquery.

search_viasocket_docsA
Read-onlyIdempotent
Inspect

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

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources