API Tools

viasocket.com

Provides tools to search viaSocket documentation, browse API docs, call viaSocket API endpoints, and inspect plugins and authentication versions.

1 endpoint15 known toolsFirst detected November 1, 2026Last detected November 1, 2026

ENDPOINT 1

https://connect.viasocket.com/mcp

No auth detected

MCP server metadata

Name: viasocket-mcp
Version: 1.0.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Server instructions

viaSocket MCP: Developer Hub (plugins, SDK), automations (flows) and a product's own MCP server. Load the quickstart-viasocket-developer-hub skill before any task. - Plug, action, trigger or connection work: fetch https://flow.viasocket.com/documentation/plugs/skills/index.md raw, pick one guide, read it whole, follow it. Integrating viaSocket into the user's product: https://flow.viasocket.com/documentation/skill.md, read whole. The product's own MCP server: https://flow.viasocket.com/documentation/skill/mcp.md (mint VIASOCKET_MCP_TOKEN here: GET https://flow-api.viasocket.com/mcp/agent-token; then npx viasocket-apps mcp). Deploying a finished app: Embarko's guide, https://embarko.ai/docs/quickstart.md. - Automations: all 13 flow endpoints are POST https://flow.sokt.io/func/<id> via call_any_api_of_viasocket. Order: List Flows, Search Services, List Actions/Triggers, List Connections (Create Connection Link if none), Build Trigger/Action Input. Create Empty Flow, Save Trigger, Save Steps only after the user confirms; Save Steps replaces all steps, so Get Flow first. Never Run Action Once unless the user agrees. - Other reads: call_any_read_api_of_viasocket; writes: call_any_api_of_viasocket with the documented body. Both reach only viaSocket endpoints documented here; never Embarko, mcp.viasocket.com or any other service. - Embarko deploy (only after a yes): own sign-in (email -> deploy token the person pastes), then Authorization: Bearer <Embarko token> to https://ship.embarko.ai. Never mix viaSocket and Embarko tokens. - Never show client secrets, the signing secret, the MCP token or the Embarko token. Confirm before creating, publishing, deleting or deploying. - Plugs: fix or extend the user's own (list_plugins); build one for an app that has none; after publishing, call report_published. viaSocket's plugs: never edit; report_feedback (missing action/trigger/field = missing_capability). Report breakage, wrong docs, user corrections.

Known tools 15

search_viasocket_docs

Search the viaSocket documentation with a natural-language question.

Inferred read-only

get_viasocket_api_docs

Browse the viaSocket API docs, one level at a time.

Inferred read-only

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

Potential side effects

list_plugins

List every viaSocket Developer Hub plugin (app) the user's organization owns.

Inferred read-only

list_auth_versions

List a plugin's authentication versions (filter=getAuthDetails, identifier=<pluginId>) to find an authid.

Inferred read-only

list_actions_and_triggers

List a plugin's actions and triggers (filter=getAllActions, identifier=<pluginId>), or get one (filter=getActionDetails, identifier=<actionId>).

Inferred read-only

list_action_versions

List all versions of an action or trigger (filter=getActionVersions, identifier=<actionId>), with code, inputs, authid, status and verification status.

Inferred read-only

get_plugin_analytics

Get run counts, error counts and flow counts for every action and trigger version of a plugin (filter=getPluginDetails, identifier=<pluginId>, optional startTime and endTime dates).

Inferred read-only

get_org_details_by_token

Get the viaSocket organization (id and details) that the signed-in user's token belongs to.

Inferred read-only

list_embed_projects

List an organization's embed projects (type=embed) for viaSocket SDK setup.

Inferred read-only

call_any_read_api_of_viasocket

Read from any viaSocket API endpoint with a GET request for the user and return its response.

Inferred read-only

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.

Inferred read-only

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.

Potential side effects

get_viasocket_embed_secret

Gets the viaSocket organization's embed signing secret (VIASOCKET_EMBED_SECRET) into the developer's .

Inferred read-only

quickstart-viasocket-developer-hub

Quickstart for viaSocket: build and manage your viaSocket plugins (apps) in the Developer Hub (auth, actions, triggers, versions, reusable components, debugging), set up a product's viaSocket keys, give a product its own MCP server, and build automations (flows) for the user: find apps, connect accounts, create flows, set triggers and write steps.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.viasocket-mcp]
url = "https://connect.viasocket.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: viasocket-mcp
Remote MCP URL: https://connect.viasocket.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "viasocket-mcp",
  "transport": "streamable-http",
  "url": "https://connect.viasocket.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.