mcpField
V
viaSocket

viaSocket

Remote
viasocket.comDeveloper Tools0Updated 1d ago

About viaSocket

viaSocket MCP lets AI assistants build and manage plugins in the Developer Hub, create automations, and connect products to other apps through the SDK. Documentation tools work without sign-in; account operations use OAuth.

Key features

  1. 01Search viaSocket and API documentation
  2. 02Manage plugins, actions, triggers, and versions
  3. 03View plugin analytics
  4. 04Retrieve organization and embed project details
  5. 05Call viaSocket read and write APIs

Use cases

  1. 01Look up Developer Hub development documentation
  2. 02Manage plugins and their actions or triggers
  3. 03Review plugin analytics
  4. 04Connect a product through viaSocket APIs

MCP support

This is a Streamable HTTP remote MCP server at https://connect.viasocket.com/mcp. MCP clients can use its documentation, plugin, account, SDK, and API tools; documentation tools need no sign-in, while other operations use OAuth.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://connect.viasocket.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

viaSocket

viaSocket MCP

Lets AI assistants work with viaSocket: build and manage your plugins (apps) in the Developer Hub, create automations (flows), and connect your product to other apps with the viaSocket SDK.

This is a remote MCP server (Streamable HTTP) at https://connect.viasocket.com/mcp. Nothing to install: your AI tool connects to it, and you sign in to viaSocket once through OAuth (the same account as viasocket.com). The docs tools work without signing in.

Tools

AreaTools
Docssearch_viasocket_docs, get_viasocket_api_docs, quickstart-viasocket-developer-hub
Plugins (Developer Hub)list_plugins, list_auth_versions, list_actions_and_triggers, list_action_versions, get_plugin_analytics, report_published
Account and SDKget_org_details_by_token, list_embed_projects, get_viasocket_embed_secret
Any viaSocket APIcall_any_read_api_of_viasocket (GET), call_any_api_of_viasocket (POST, PUT, PATCH, DELETE)
Feedbackreport_feedback

Connect from Cline

Install it from the Cline MCP Marketplace, or open MCP Servers → Configure MCP Servers and add this to cline_mcp_settings.json:

{
  "mcpServers": {
    "viasocket": {
      "type": "streamableHttp",
      "url": "https://connect.viasocket.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

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.

Connect from Claude Code

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

then run /mcp and sign in.

MCP Registry

server.json is the listing for the official MCP Registry, as com.viasocket/mcp. The com.viasocket name is proven by owning the viasocket.com domain.

One-time setup: create a signing key and publish its public half on viasocket.com (Git Bash or any shell with OpenSSL):

openssl genpkey -algorithm Ed25519 -out mcp-registry-key.pem
echo "v=MCPv1; k=ed25519; p=$(openssl pkey -in mcp-registry-key.pem -pubout -outform DER | tail -c 32 | base64)"

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

Publish (bump version first for any later change):

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')"
mcp-publisher publish

Links

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.