Categories › AI & Agents › Multi-agent, orchestration & workflows
Use your apps from your AI: Gmail, Slack, Google Sheets, HubSpot and 2,300+ more on your accounts.
Remote server: your requests and data go to connect.viasocket.com. Claude Code: claude mcp add --transport http viasocket https://connect.viasocket.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 descrcall_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, plist_plugins — List every viaSocket Developer Hub plugin (app) the user's organization owns. Send filter=getAllPlugins and identifier equal to the orgId inlist_auth_versions — List a plugin's authentication versions (filter=getAuthDetails, identifier=<pluginId>) to find an authid. Responses include decrypted clientlist_actions_and_triggers — List a plugin's actions and triggers (filter=getAllActions, identifier=<pluginId>), or get one (filter=getActionDetails, identifier=<actionIlist_action_versions — List all versions of an action or trigger (filter=getActionVersions, identifier=<actionId>), with code, inputs, authid, status and verificatget_plugin_analytics — Get run counts, error counts and flow counts for every action and trigger version of a plugin (filter=getPluginDetails, identifier=<pluginIdget_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 ylist_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). 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 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 capabilitreport_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 cget_viasocket_embed_secret — Gets the viaSocket organization's embed signing secret (VIASOCKET_EMBED_SECRET) into the developer's .env encrypted, so you never see it. Uslist_connections — The app accounts the signed-in user has already connected to viaSocket. Body {} answers rows with auth_id, service_id, service_name and conncreate_connection_link — Make a sign-in link so the user connects an app account (Google, Slack, an API key…) to viaSocket. Body { "service_ids": ["<service_id>"] } 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 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 { "searchqlist_app_actions — List what an app can do for the user. Body { "serviceId": "<service_id from search_apps>" } (camelCase) answers actions[] with action_id, acget_request_status — Check a request you filed with report_feedback, by the requestId it returned. Use it for a missing app, action, trigger or field (kind missiquickstart-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+ apNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.