search_viasocket_docs — viaSocket MCP Tool Read-only
search_viasocket_docs
(search viasocket docs) is one of 20 tools on the
viaSocket
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_viasocket_docs from your client
- Claude Code viaSocket search_viasocket_docs run in your project directory
- Claude Desktop viaSocket search_viasocket_docs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor viaSocket search_viasocket_docs ~/.cursor/mcp.json
- VS Code viaSocket search_viasocket_docs .vscode/mcp.json
- Zed viaSocket search_viasocket_docs ~/.config/zed/settings.json
- Windsurf viaSocket search_viasocket_docs ~/.codeium/windsurf/mcp_config.json
- Cline viaSocket search_viasocket_docs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI viaSocket search_viasocket_docs ~/.gemini/settings.json
- Grok viaSocket search_viasocket_docs .mcp.json (in your project root)
- ChatGPT viaSocket search_viasocket_docs Settings → Connectors → Advanced → Developer mode
- Claude.ai viaSocket search_viasocket_docs Settings → Connectors → Add custom connector
- LangChain viaSocket search_viasocket_docs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://connect.viasocket.com/mcp
Other tools on this server
- get_viasocket_api_docs
- call_any_api_of_viasocket
- list_plugins
- list_auth_versions
- list_actions_and_triggers
- list_action_versions
- get_plugin_analytics
- get_org_details_by_token
- list_embed_projects
- call_any_read_api_of_viasocket
- report_feedback
- report_published
- get_viasocket_embed_secret
- list_connections
- create_connection_link
- run_app_action
- search_apps
- list_app_actions
- quickstart-viasocket-developer-hub
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.