原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Sanka

作者:sankaHQ版本 1.0.0i★ 0i在云端运行官方网站 ↗
注册名称io.github.sankaHQ/sanka-mcp

安装方法

能做什么

Sanka Desk IT requests, Sanka Flow records, approvals, workflows and app migrations, with OAuth.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 连接时登录该服务(OAuth)
  • 分类 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Sanka。按照 https://mcp.popnx.com/i/sankahq-sanka-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.sanka.com) · ✓ 命令已检查 2026年11月20日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Sanka
    Remote MCP server URL · 地址https://mcp.sanka.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsSanka

  4. 试一试

    用 Sanka 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Sanka,或回答中出现 Sanka 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Sanka
    Connection · 地址https://mcp.sanka.com/mcp
  3. 在聊天中选择 Sanka

    开启新聊天,输入前先从插件列表中选择 Sanka

  4. 试一试

    用 Sanka 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Sanka,或回答中出现 Sanka 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user sanka https://mcp.sanka.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Sanka 在列表中并显示已连接

  4. 试一试

    用 Sanka 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Sanka,或回答中出现 Sanka 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Sanka 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Sanka,或回答中出现 Sanka 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Sanka 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Sanka,或回答中出现 Sanka 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.sanka.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Sanka 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user sanka https://mcp.sanka.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sanka": {
      "url": "https://mcp.sanka.com/mcp"
    }
  }
}

VS Code (mcp.json)

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

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
许可证i
Apache-2.0
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.0.0
分类i
其他
发布到注册中心i
2026年11月20日
代码最后更新i
2026年11月20日
最近检查
2026年11月20日
作者
sankaHQ
网站
sanka.com
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 sankaHQ 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✓ 通过

    端点有响应

    在 353 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/sankahq-sanka-mcp.svg)](https://mcp.popnx.com/en/servers/sankahq-sanka-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 20958 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 20958 个服务器的 99% 更新
  • 基础检查结果等于或优于此分类中其他 20958 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Sanka 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(1.0.0)于今天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万4天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92762个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582414个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
Sanka
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/54/44/44/41/44/4
许可证Apache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Sanka MCP Server

This repository contains the hosted Sanka MCP service and the TypeScript client it uses to call Sanka's externally callable API surface. It is now maintained as a normal TypeScript workspace, not as a Stainless-managed repository.

The production service is a remote Streamable HTTP MCP endpoint:

  • POST /mcp as the primary endpoint
  • POST /sse as a compatibility alias for clients that still expect an SSE-style path
  • POST / as a compatibility alias
  • GET /health for health checks

The /mcp endpoint exposes both the general SDK tools and the read-only CRM tools from a single MCP surface.

Live endpoints:

  • https://mcp.sanka.com/mcp
  • https://mcp.sanka.com/sse

Staging endpoint:

  • https://sanka-mcp-staging.fly.dev/mcp

Repository layout

  • src/: TypeScript client for Sanka's externally callable API surface, used by the MCP service
  • src/internal/: package-private SDK runtime helpers, not Sanka private backend code
  • packages/mcp-server/: the MCP server application and Docker entrypoint
  • .github/workflows/: CI plus staging and production Fly deployment workflows
  • fly.toml: production Fly app configuration
  • fly.staging.toml: staging Fly app configuration
  • docs/openapi-maintenance.md: guidance for keeping API coverage current without Stainless

Auth

The hosted server is a standard MCP OAuth 2.1 protected resource (MCP authorization spec 2026-07-28). Sanka (sanka-api) is the authorization server, issuer https://api-v2.sanka.com/oauth/mcp; the consent page is https://app.sanka.com/oauth/mcp/authorize.

  • Every MCP request needs Authorization: Bearer . Without one the server answers 401 with WWW-Authenticate: Bearer scope="mcp:access", resource_metadata="…"; an invalid or expired token adds error="invalid_token".
  • Each endpoint is its own resource, named by the URL clients connect to: https://mcp.sanka.com/mcp, https://mcp.sanka.com/sse and https://mcp.sanka.com. Its RFC 9728 metadata is at /.well-known/oauth-protected-resource/mcp, …/sse and /.well-known/oauth-protected-resource. A token is bound to one resource.
  • /.well-known/oauth-authorization-server mirrors Sanka's metadata for clients built for the 2025-03-26 protocol.
  • Clients register with a Client ID Metadata Document (preferred) or dynamic client registration, and always use PKCE (S256); Sanka issues no client secrets.
  • The server never passes the client's token to the business API. It exchanges it through POST /oauth/internal/mcp-oauth-token (authenticated with MCP_SERVER_OAUTH_RESOURCE_SERVER_SECRET, shared with sanka-api only) for its own short-lived API token bound to the same connection. Sanka checks the connection on every API call, so disconnecting a client takes effect at once.
  • switch_workspace moves the whole connection to the chosen workspace, so later token exchanges and record URLs follow it.
  • The server keeps no MCP session: a client-sent mcp-session-id is ignored and never forwarded. Developer API keys (X-Sanka-API-Key) are refused.

The ChatGPT connector keeps its own resource at /chatgpt with its own issuer (https://api-v2.sanka.com/oauth/chatgpt).

Local development

pnpm install

pnpm build export MCP_SERVER_OAUTH_ISSUER="http://localhost:8000/oauth/mcp" export MCP_SERVER_INTERNAL_AUTHORIZATION_SERVER_URL="http://localhost:8000" export MCP_SERVER_OAUTH_RESOURCE_SERVER_SECRET=" " export MCP_SERVER_RESOURCE_URL="http://localhost:8080/mcp" export SANKA_BASE_URL="http://localhost:8000" node packages/mcp-server/dist/index.js --transport=http --port=8080

The local API needs the matching settings: MCP_OAUTH_ISSUER, MCP_OAUTH_AUTHORIZE_URL (the local React app's /oauth/mcp/authorize), MCP_OAUTH_RESOURCES (a JSON list with http://localhost:8080/mcp and the other local endpoints) and the same MCP_OAUTH_RESOURCE_SERVER_SECRET.

Stdio remains a local-development transport. SANKA_API_KEY there is process configuration, not a client-supplied bearer mode.

Then verify:

curl http://127.0.0.1:8080/health

curl -sS -D - http://127.0.0.1:8080/mcp \ -H 'content-type: application/json' \ -H 'accept: application/json, text/event-stream' \ --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0.1"}}}'

The initialize request answers 401 with the WWW-Authenticate challenge. Point an HTTP MCP client (for example the MCP Inspector) at http://127.0.0.1:8080/mcp without static auth headers; it discovers the authorization server, opens the Sanka consent page, and retries with its token. curl http://127.0.0.1:8080/.well-known/oauth-protected-resource/mcp shows the resource metadata.

Browser Use worker

The browser_use MCP tool dispatches allowlisted browser workflows to a separate worker. The MCP server keeps session authentication, audit metadata, workflow routing, and confirmation gates; the worker owns browser state and third-party UI interaction. The first registered workflow is:

  • demo.hubspot.company_avatar: update HubSpot demo company avatars through the HubSpot UI when CRM APIs cannot set the visible avatar.

Run a local worker with agent-browser:

npm install -g agent-browser

agent-browser install

export SANKA_BROWSER_USE_WORKER_TOKEN="local-worker-token" export SANKA_BROWSER_USE_PROFILE_ROOT=".browser-use-profiles" export SANKA_BROWSER_USE_ARTIFACT_DIR=".browser-use-artifacts" pnpm --dir packages/mcp-server browser-use-worker

Point the MCP server at it:

export SANKA_BROWSER_USE_WORKER_URL="http://127.0.0.1:8787/run"

export SANKA_BROWSER_USE_WORKER_TOKEN="local-worker-token"

For production, deploy the worker as a separate service, for example on Fly, with a persistent volume mounted at SANKA_BROWSER_USE_PROFILE_ROOT so HubSpot login cookies survive restarts. Keep the worker private or token-protected and only expose /run to the MCP service.

See docs/browser-use-worker-fly.md for the Fly worker app, persistent volume, secret wiring, and profile seeding runbook.

Deployment

This repo deploys to Fly from packages/mcp-server/Dockerfile.

  • Manual production deploy: fly deploy -c fly.toml
  • Manual staging deploy: fly deploy -c fly.staging.toml
  • Automatic staging deploy: push to staging
  • Automatic production deploy: publish a GitHub release that targets main

Release Flow

Use the same promotion shape as the main Sanka app:

  1. Open feature PRs into staging.
  2. Merge staging after CI passes to deploy sanka-mcp-staging.
  3. Validate the staging MCP endpoint.
  4. Open staging -> main.
  5. After main is ready, run Create new Sanka MCP Tag and Release.
  6. The published release deploys production.

Required Fly apps and secrets:

  • Production app: sanka-mcp
  • Staging app: sanka-mcp-staging
  • Set the same MCP_SERVER_* secrets on both apps unless staging intentionally uses a different auth stack.

Retry policy

The TypeScript client retries 408, 409, 429, 5xx and connection errors twice by default. Only tools with metadata.operation: 'read' keep those automatic retries. Every write tool calls the API once and returns any error to the agent: a write can fail after its side effect happened, such as an email Gmail accepted before Sanka recorded it, and a retry would repeat it. The API also marks errors from delivery routes with x-should-retry: false. Reply tools report DELIVERY_UNKNOWN as a do-not-resend error.

Maintenance direction

This repository no longer depends on Stainless project access at runtime or for ongoing development. API coverage should be maintained directly in this repo.

The recommended next step is to adopt open-source OpenAPI tooling for updates to the TypeScript client, rather than reintroducing a hosted generator dependency. See openapi-maintenance.md.

The repo now includes a starter typegen command:

pnpm generate:openapi-types

By default it reads the sibling Sanka spec at ../sanka-sdks/openapi.json.

Developer Cloud (release candidate)

The hosted tools expose the same V2 source, run, receipt, certificate and Fleet contracts as the CLI and SDKs. This source change does not enable production execution. Read get_developer_cloud_availability first and obey each capability's availability flag. Free local migration and client-evidence registration are unchanged.

Every call takes a pinned workspace_id. Paid creates and selective retries require an explicit request, approved cap, confirm: true, and stable idempotency_key. Existing user authorization is sufficient. A lost response must not create a new intent: read back or replay the identical key and request. No tool purchases credits, creates repository PRs, merges, or deploys.

  • Source/run: upload_developer_cloud_source, create_developer_cloud_run, list_developer_cloud_runs, get_developer_cloud_run, cancel_developer_cloud_run.
  • Evidence: list_developer_cloud_events, get_developer_cloud_receipt, list_developer_cloud_artifacts, download_developer_cloud_artifact.
  • Certificates: list_developer_cloud_certificate_keys, get_developer_cloud_certificate, revoke_developer_cloud_certificate.
  • Fleet: create_developer_cloud_fleet, list_developer_cloud_fleets, get_developer_cloud_fleet, cancel_developer_cloud_fleet, retry_developer_cloud_fleet.

Repair and certificate issuance use create_developer_cloud_run.request.repair and .certification, respectively. Compute is 25 credits per worker-minute, rounded once per run. Successful Repair adds 250 credits; independent certificate issuance adds 500 (1 credit = ¥1 or 1 cent since 2026-11-20). All compute and premiums remain within the approved cap. Failed gates have no premium. Fleet adds no surcharge: its cap is the sum of explicit child caps, reserved atomically, with at most five active workers per workspace. Retry selects only failed children after the original Fleet settles; it creates a new Fleet and preserves completed children's receipts.

Upload the exact ZIP digest and declared full revision; the service pins uploaded bytes but does not independently prove their Git provenance. Inspect certificate scope, scenarios, limitations and revocation. Downloading a certificate does not verify its signature: use the CLI's offline verification with the published key. Artifact downloads verify bytes against recorded SHA-256 metadata. MCP supports up to 64 MiB; larger artifacts use the CLI/API. Large downloads use the existing session-bound URL or read_binary_download_chunk flow.

Request-schema regeneration uses the shared V2 SDK input:

python3 scripts/sync-developer-cloud-contract.py ../sanka-sdks/openapi.json

pnpm exec prettier --write packages/mcp-server/src/generated/developer-cloud-schemas.ts

Embedded workspace

The Sanka app opens the connected full Flow workspace: its sidebar, dashboards, record tables, workflows and reports. Full workspace access requires explicit Sanka authorization. Connections with narrower access show the authorization controls; the earlier Invoice assistant pilot screen is no longer offered.

The hosted invoice MCP tools remain available under their existing scopes and confirmation requirements. Removing the pilot screen does not change invoice records or the API contract.