Build viaSocket plugins and automations, and connect your product to other apps.
Maintain this server? Claim it
Try it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
call_any_api_of_viasocket Destructive
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.
Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here.
HTTP method from the endpoint's docs
Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {"proxy_auth_token": "", "Content-Type": "application/json"}
JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body.
Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true}
The server marks this tool as destructive. Running it may delete or overwrite data on the server or in any account you connected with your headers.
Install
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http mcp https://connect.viasocket.com/mcp
Tools (15)
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, 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.
destructive
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.
| Argument | Type | Description |
|---|---|---|
| url* | string | Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here. |
| body | object | JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body. |
| query | object | Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true} |
| method* | string | HTTP method from the endpoint's docs |
| headers* | object | Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {"proxy_auth_token": "", "Content-Type": "application/json"} |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url",
"headers",
"method"
],
"properties": {
"url": {
"type": "string",
"description": "Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here."
},
"body": {
"type": "object",
"description": "JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"query": {
"type": "object",
"description": "Query params as name/value pairs; an array sends the param once per item. Example: {\"type\": \"flow\", \"bringflows\": true}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH",
"DELETE"
],
"type": "string",
"description": "HTTP method from the endpoint's docs"
},
"headers": {
"type": "object",
"description": "Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value \"\" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {\"proxy_auth_token\": \"\", \"Content-Type\": \"application/json\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
}
}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 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.
read-only
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.
| Argument | Type | Description |
|---|---|---|
| url* | string | Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here. |
| query | object | Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true} |
| headers* | object | Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {"proxy_auth_token": "", "Content-Type": "application/json"} |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"url",
"headers"
],
"properties": {
"url": {
"type": "string",
"description": "Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here."
},
"query": {
"type": "object",
"description": "Query params as name/value pairs; an array sends the param once per item. Example: {\"type\": \"flow\", \"bringflows\": true}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"headers": {
"type": "object",
"description": "Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value \"\" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {\"proxy_auth_token\": \"\", \"Content-Type\": \"application/json\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
}
}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 the user for it.
read-only
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.
No arguments.
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}get_plugin_analyticsGet 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).
read-only
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).
| Argument | Type | Description |
|---|---|---|
| orgId* | string | Your viaSocket organization id |
| filter | string | Required (access check). Use getPluginDetails. e.g. getPluginDetails |
| endTime | string | Optional end date. e.g. 2026-10-19 |
| startTime | string | Optional start date. e.g. 2026-10-01 |
| identifier | string | Required. Plugin id |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orgId"
],
"properties": {
"orgId": {
"type": "string",
"description": "Your viaSocket organization id"
},
"filter": {
"type": "string",
"description": "Required (access check). Use getPluginDetails. e.g. getPluginDetails"
},
"endTime": {
"type": "string",
"description": "Optional end date. e.g. 2026-10-19"
},
"startTime": {
"type": "string",
"description": "Optional start date. e.g. 2026-10-01"
},
"identifier": {
"type": "string",
"description": "Required. Plugin id"
}
}
}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 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.
read-only
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.
| Argument | Type | Description |
|---|---|---|
| path | string | A link from a listing, exactly as given (e.g. "https://docs.example.com/sms/llms.txt" or ".../sms/send-sms.openapi.yml"), or just the path ("sms", "sms/send-sms.openapi.yml"). Leave it out for the top level. |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"path": {
"type": "string",
"description": "A link from a listing, exactly as given (e.g. \"https://docs.example.com/sms/llms.txt\" or \".../sms/send-sms.openapi.yml\"), or just the path (\"sms\", \"sms/send-sms.openapi.yml\"). Leave it out for the top level."
}
}
}get_viasocket_embed_secretGets 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.
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.
| Argument | Type | Description |
|---|---|---|
| orgId* | string | The orgId the key is created for |
| publicKey* | string | The publicKey printed by `docstar-cli key request`, exactly as printed |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"publicKey",
"orgId"
],
"properties": {
"orgId": {
"type": "string",
"description": "The orgId the key is created for"
},
"publicKey": {
"type": "string",
"description": "The publicKey printed by `docstar-cli key request`, exactly as printed"
}
}
}list_action_versionsList all versions of an action or trigger (filter=getActionVersions, identifier=<actionId>), with code, inputs, authid, status and verification status. Use fields to keep the response small.
read-only
List all versions of an action or trigger (filter=getActionVersions, identifier=<actionId>), with code, inputs, authid, status and verification status. Use fields to keep the response small.
| Argument | Type | Description |
|---|---|---|
| orgId* | string | Your viaSocket organization id |
| fields | string | Optional comma-separated columns, e.g. rowid,versionid,status,verificationstatus |
| filter | string | Required. Must be getActionVersions. e.g. getActionVersions |
| identifier | string | Required. Action id |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orgId"
],
"properties": {
"orgId": {
"type": "string",
"description": "Your viaSocket organization id"
},
"fields": {
"type": "string",
"description": "Optional comma-separated columns, e.g. rowid,versionid,status,verificationstatus"
},
"filter": {
"type": "string",
"description": "Required. Must be getActionVersions. e.g. getActionVersions"
},
"identifier": {
"type": "string",
"description": "Required. Action id"
}
}
}list_actions_and_triggersList a plugin's actions and triggers (filter=getAllActions, identifier=<pluginId>), or get one (filter=getActionDetails, identifier=<actionId>). Use it to find an actionId.
read-only
List a plugin's actions and triggers (filter=getAllActions, identifier=<pluginId>), or get one (filter=getActionDetails, identifier=<actionId>). Use it to find an actionId.
| Argument | Type | Description |
|---|---|---|
| orgId* | string | Your viaSocket organization id |
| fields | string | Optional comma-separated columns, e.g. rowid,name,type,status |
| filter | string | Required. getAllActions (by plugin) or getActionDetails (one action by rowid). e.g. getAllActions |
| identifier | string | Required. Plugin id for getAllActions; action id for getActionDetails |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orgId"
],
"properties": {
"orgId": {
"type": "string",
"description": "Your viaSocket organization id"
},
"fields": {
"type": "string",
"description": "Optional comma-separated columns, e.g. rowid,name,type,status"
},
"filter": {
"type": "string",
"description": "Required. getAllActions (by plugin) or getActionDetails (one action by rowid). e.g. getAllActions"
},
"identifier": {
"type": "string",
"description": "Required. Plugin id for getAllActions; action id for getActionDetails"
}
}
}list_auth_versionsList a plugin's authentication versions (filter=getAuthDetails, identifier=<pluginId>) to find an authid. Responses include decrypted client secrets: never show them to the user.
read-only
List a plugin's authentication versions (filter=getAuthDetails, identifier=<pluginId>) to find an authid. Responses include decrypted client secrets: never show them to the user.
| Argument | Type | Description |
|---|---|---|
| orgId* | string | Your viaSocket organization id |
| fields | string | Optional comma-separated columns |
| filter | string | Required. getAuthDetails (all of a plugin's auth versions) or updateAuthDetails (one auth version by rowid). e.g. getAuthDetails |
| identifier | string | Required. Plugin id for getAuthDetails; auth version rowid for updateAuthDetails |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orgId"
],
"properties": {
"orgId": {
"type": "string",
"description": "Your viaSocket organization id"
},
"fields": {
"type": "string",
"description": "Optional comma-separated columns"
},
"filter": {
"type": "string",
"description": "Required. getAuthDetails (all of a plugin's auth versions) or updateAuthDetails (one auth version by rowid). e.g. getAuthDetails"
},
"identifier": {
"type": "string",
"description": "Required. Plugin id for getAuthDetails; auth version rowid for updateAuthDetails"
}
}
}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 call_any_api) after the developer confirms.
read-only
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.
| Argument | Type | Description |
|---|---|---|
| type | string | Required. `embed` for SDK projects (`flow` and `default` are the workspace's own automation projects). e.g. embed |
| orgId* | string | Organization id from Find Organizations or Get Org Details By Token |
| bringflows | string | Optional. true also returns the flows of each project. e.g. false |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orgId"
],
"properties": {
"type": {
"type": "string",
"description": "Required. `embed` for SDK projects (`flow` and `default` are the workspace's own automation projects). e.g. embed"
},
"orgId": {
"type": "string",
"description": "Organization id from Find Organizations or Get Org Details By Token"
},
"bringflows": {
"type": "string",
"description": "Optional. true also returns the flows of each project. e.g. false"
}
}
}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).
read-only
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).
| Argument | Type | Description |
|---|---|---|
| orgId* | string | Your viaSocket organization id |
| fields | string | Optional comma-separated list of columns to return, e.g. rowid,name,status,iconurl |
| filter | string | Required. Must be getAllPlugins. e.g. getAllPlugins |
| identifier | string | Required. Your orgId (same as the path) |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"orgId"
],
"properties": {
"orgId": {
"type": "string",
"description": "Your viaSocket organization id"
},
"fields": {
"type": "string",
"description": "Optional comma-separated list of columns to return, e.g. rowid,name,status,iconurl"
},
"filter": {
"type": "string",
"description": "Required. Must be getAllPlugins. e.g. getAllPlugins"
},
"identifier": {
"type": "string",
"description": "Required. Your orgId (same as the path)"
}
}
}quickstart-viasocket-developer-hubQuickstart 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. Routes plug work through the plug skills index, product integration and the product's MCP server 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.
read-only
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. Routes plug work through the plug skills index, product integration and the product's MCP server 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.
No arguments.
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}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 (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.
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.
| Argument | Type | Description |
|---|---|---|
| env | object | e.g. {"sdkVersion":"0.7.0","framework":"nextjs","language":"typescript","client":"claude-code"} |
| kind | string | e.g. error |
| refs | object | e.g. {"app":"slack","pluginId":"rowslack123","actionId":"rowsendmsg01","requestId":"req_abc"} |
| error | object | e.g. {"status":500,"code":"INTERNAL","message":"failed"} |
| stage | string | e.g. actions_and_events |
| actual | string | e.g. 500 INTERNAL |
| intent | string | e.g. Post to a Slack channel when an order is created |
| source | string | e.g. action |
| retries | number | e.g. 2 |
| expected | string | e.g. Message posted |
| feedback | string | e.g. Slack Send Message returns 500 on valid input; same call worked yesterday |
| severity | string | e.g. degraded |
| attempted | string | e.g. Ran Send Message with channel and text from the document's sample |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"env": {
"type": "object",
"description": "e.g. {\"sdkVersion\":\"0.7.0\",\"framework\":\"nextjs\",\"language\":\"typescript\",\"client\":\"claude-code\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"kind": {
"type": "string",
"description": "e.g. error"
},
"refs": {
"type": "object",
"description": "e.g. {\"app\":\"slack\",\"pluginId\":\"rowslack123\",\"actionId\":\"rowsendmsg01\",\"requestId\":\"req_abc\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"error": {
"type": "object",
"description": "e.g. {\"status\":500,\"code\":\"INTERNAL\",\"message\":\"failed\"}",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"stage": {
"type": "string",
"description": "e.g. actions_and_events"
},
"actual": {
"type": "string",
"description": "e.g. 500 INTERNAL"
},
"intent": {
"type": "string",
"description": "e.g. Post to a Slack channel when an order is created"
},
"source": {
"type": "string",
"description": "e.g. action"
},
"retries": {
"type": "number",
"description": "e.g. 2"
},
"expected": {
"type": "string",
"description": "e.g. Message posted"
},
"feedback": {
"type": "string",
"description": "e.g. Slack Send Message returns 500 on valid input; same call worked yesterday"
},
"severity": {
"type": "string",
"description": "e.g. degraded"
},
"attempted": {
"type": "string",
"description": "e.g. Ran Send Message with channel and text from the document's sample"
}
}
}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), 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.
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.
| Argument | Type | Description |
|---|---|---|
| app | string | e.g. Tally |
| note | string | e.g. Published privately with 4 actions and 1 trigger; OAuth 2.0 connection |
| pluginId | string | e.g. rowtally12345 |
| actionIds | array | e.g. ["rowaction1234","rowtrigger567"] |
| published | string | e.g. new_plug |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"app": {
"type": "string",
"description": "e.g. Tally"
},
"note": {
"type": "string",
"description": "e.g. Published privately with 4 actions and 1 trigger; OAuth 2.0 connection"
},
"pluginId": {
"type": "string",
"description": "e.g. rowtally12345"
},
"actionIds": {
"type": "array",
"items": {},
"description": "e.g. [\"rowaction1234\",\"rowtrigger567\"]"
},
"published": {
"type": "string",
"description": "e.g. new_plug"
}
}
}search_viasocket_docsSearch the viaSocket documentation with a natural-language question. Returns the most relevant passages with their page URLs.
read-only
Search the viaSocket documentation with a natural-language question. Returns the most relevant passages with their page URLs.
| Argument | Type | Description |
|---|---|---|
| query* | string | What to look for, e.g. "how do I send a WhatsApp template message" |
Input schema (JSON)
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "What to look for, e.g. \"how do I send a WhatsApp template message\""
}
}
}Security checkA100/100
We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Oct 30, 2026.
- Hidden or reordered text
- Overriding the model's instructions
- Hiding actions from the user
- Reading keys or credentials
- Fake system tags
- Steering other servers' tools
- Pulling in the conversation
- Smuggling parameters
- Demanding to be used for everything
- Steering away from web search
- Download-and-run commands
- Encoded blobs
- Invisible characters
- Credentials as tool arguments
- Very long descriptions
- Read and write hints