Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

Sanka

by sankaHQversion 1.0.0i★ 0iRuns in the cloudOfficial site ↗
Registry nameio.github.sankaHQ/sanka-mcp

How to install

What it does

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

  • Connects Runs in the cloud
  • Account or key Sign in to the service when you connect (OAuth)
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering8/8The cloud endpoint answered at the last check
Usage score20/100

Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Sanka. Follow https://mcp.popnx.com/i/sankahq-sanka-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 5/5 checks · What you ask goes through the maker’s server (mcp.sanka.com) · ✓ Commands checked Nov 20, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameSanka
    Remote MCP server URL · Addresshttps://mcp.sanka.com/mcp

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +ConnectorsSanka

  4. Try it

    Use Sanka and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Sanka or shows a Sanka tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · NameSanka
    Connection · Addresshttps://mcp.sanka.com/mcp
  3. Pick Sanka in a chat

    Start a new chat and pick Sanka from your plugins before typing

  4. Try it

    Use Sanka and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using Sanka or shows a Sanka tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user sanka https://mcp.sanka.com/mcp
  3. Type /mcp in Claude Code

    You should see Sanka listed as connected

  4. Try it

    Use Sanka and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Sanka or shows a Sanka tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

  1. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use Sanka and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Sanka or shows a Sanka tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

  1. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use Sanka and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Sanka or shows a Sanka tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://mcp.sanka.com/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Sanka💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

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"
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
Apache-2.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.0.0
Categoryi
Other
Published to registryi
Nov 20, 2026
Code last changedi
Nov 20, 2026
Last checked
Nov 20, 2026
Maker
sankaHQ
Website
sanka.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

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

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account sankaHQ, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • ✓ Pass

    Endpoint responds

    Responded in 353 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

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

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20958 servers in this category
  • Published to the registry more recently than 99% of the other 20958 servers in this category
  • Basic checks equal to or better than 99% of the other 20958 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sanka safe?

It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed today, and the latest version (1.0.0) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

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

by koala73Widely used★ 90.9KUpdated 4 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

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

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 31 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

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

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

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

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Sanka
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks5/54/44/44/41/44/4
LicenseApache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.