Use your apps from your AI: Gmail, Slack, Google Sheets, HubSpot and 2,300+ more on your accounts.
MCPpedia last refreshed this data
com.viasocket.mcp/mcp is an MCP server that use your apps from your AI: Gmail, Slack, Google Sheets, HubSpot and 2,300+ more on your accounts. Its tool list has not been published yet over http, requires no API key, and scores 40/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"viasocket": {
"url": "https://connect.viasocket.com/mcp",
"type": "streamableHttp",
"disabled": false,
"autoApprove": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Use your apps from your AI: Gmail, Slack, Google Sheets, HubSpot and 2,300+ more on your accounts.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for com.viasocket.mcp/mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.

Lets AI assistants use your apps through viaSocket: send an email, post to Slack, add a sheet row, read a CRM, on your own Gmail, Slack, Google Sheets, HubSpot or any of 2,300+ apps; automate across them; build and manage your plugins (apps) in the Developer Hub; 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.
| Area | Tools |
|---|---|
| Docs | search_viasocket_docs, get_viasocket_api_docs, quickstart-viasocket-developer-hub |
| Your apps | search_apps, list_app_actions, list_connections, create_connection_link, run_app_action |
| Plugins (Developer Hub) | list_plugins, list_auth_versions, list_actions_and_triggers, list_action_versions, get_plugin_analytics, report_published |
| Account and SDK | get_org_details_by_token, list_embed_projects, get_viasocket_embed_secret |
| Any viaSocket API | call_any_read_api_of_viasocket (GET), call_any_api_of_viasocket (POST, PUT, PATCH, DELETE) |
| Feedback | report_feedback |
Using your apps (the connector): the guide for AI assistants is https://viasocket.com/docs/skill.md.
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.
claude mcp add --transport http viasocket https://connect.viasocket.com/mcp
then run /mcp and sign in.
server.json is the listing for the official MCP Registry, as com.viasocket.mcp/mcp. The com.viasocket.mcp name is proven by owning the viasocket.com domain (a viasocket.com DNS login covers its subdomains too).
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