viaSocket

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 채팅 및 이메일

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://connect.viasocket.com/mcp

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

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

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

https://connect.viasocket.com/mcp

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• search_viasocket_docs

  Search the viaSocket documentation with a natural-language question. Returns the most relevant passages with their page URLs.

• get_viasocket_api_docs

  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 li

• 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). For GET requests use call_any_read_api_of_viasocket. Look the endpoint up with get_viasocket_api_docs first to get its URL,

• list_plugins

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

• list_auth_versions AI에게 내리는 지시처럼 보여요

  List a plugin's authentication versions (filter=getAuthDetails, identifier= ) to find an authid. Responses include decrypted client secrets: never show them to the user.

• list_actions_and_triggers

  List a plugin's actions and triggers (filter=getAllActions, identifier= ), or get one (filter=getActionDetails, identifier= ). Use it to find an actionId.

• list_action_versions

  List all versions of an action or trigger (filter=getActionVersions, identifier= ), with code, inputs, authid, status and verification status. Use fields to keep the response small.

• get_plugin_analytics

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

• get_org_details_by_token

  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

• list_embed_projects

  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 cal

• call_any_read_api_of_viasocket

  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

• 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. 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 (t

• 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. viaSocket then reviews the published plug and may add missing actions or triggers. Body: pluginId (the plug rowid, required

• get_viasocket_embed_secret AI에게 내리는 지시처럼 보여요

  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 pa

• list_connections

  The app accounts the signed-in user has already connected to viaSocket. Body {} answers rows with auth_id, service_id, service_name and connection_label (a JSON string: parse it before showing it, e.g. the email of the Gmail account). Match service_id to find the auth_id an actio

• create_connection_link

  Make a sign-in link so the user connects an app account (Google, Slack, an API key…) to viaSocket. Body { "service_ids": [" "] } answers data[] with a connection_url per app. Give the user the link, wait until they say they signed in, then call list_connections again to get the a

• run_app_action

  Do one thing in the user's app right now, on their own account: send an email, post a message, add a row, create a record, fetch data. Body { service_id, action_id, auth_id, instructions, thread_id }: service_id from search_apps, action_id from list_app_actions, auth_id from list

• search_apps

  Find an app the user wants to use from their AI: Gmail, Slack, Google Sheets, HubSpot, Notion, Trello or any of 2,300+ apps. Body { "searchquery": "gmail" } answers services[] with service_id, service_name and service_description. This is the first step whenever the user asks to

• list_app_actions

  List what an app can do for the user. Body { "serviceId": " " } (camelCase) answers actions[] with action_id, action_name, action_description and fields_for_action_details. Use it to pick the action that matches the request (Gmail "Send Email", Google Sheets "Add Row", HubSpot "C

• quickstart-viasocket-developer-hub

  Quickstart for viaSocket: use the user's own apps from their AI (send an email, post to Slack, add a sheet row, read a CRM; any of 2,300+ apps), build automations (flows) across those apps, and for developers: build and manage viaSocket plugins in the Developer Hub, set up a prod

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 mcp.viasocket.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  550ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✕ 실패

  도구 설명에 숨겨진 지시 없음

  도구 설명 2개에 AI에게 지시하는 것처럼 보이는 글이 있어요. 설치하기 전에 아래 내용을 읽어 보세요

채팅 및 이메일 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 1766개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 1766개 중 88%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 1766개 중 44%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{

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](llms-install.md).

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

openssl genpkey -algorithm Ed25519 -out mcp-registry-key.pem

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

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')"