sanka
Sanka Plugin for Claude helps you to run your entire sales in one place: CRM, CPQ, Pipelines, Billing and more.
Open source Repository Open in the app JSON README (API)
About
Sanka Plugin for Claude helps you to run your entire sales in one place: CRM, CPQ, Pipelines, Billing and more.
Details
- Kind
- Plugins
- Topic
- Finance & crypto
- Publisher
- sankahq
- Origin
- marketplace
- Category
- ferramentas
- Last push
- 2026-09-01T10:24:10Z
- Repository state
- ativo
- Language
- JavaScript
- License
- MIT
- Added
- 2026-08-30 01:48:58
- Updated
- 2026-08-30 01:48:58
- Origin id
sankahq/sanka-plugin/sanka
README
# sanka-plugin Sanka connects local AI clients to Sanka's hosted MCP server through the packaged local proxy. Use it for live Sanka CRM, estimates, approvals, billing, private inbox, expenses, and workflow intents. Start with the general Sanka router when you do not want to choose a specific skill. ## Install Codex uses a repo-local marketplace, while Claude Code supports a GitHub marketplace command. The install paths differ, but both run the same local proxy against the hosted Sakura MCP server and expose the same `$sakura:...` skills. ### Codex ```text Clone sankaHQ/sanka-plugin Open the cloned repo in Codex Restart Codex Install Sanka from the Sanka marketplace Start with the Sakura chip or a plain $sakura:... mention ``` ### Claude Code ```text /plugin marketplace add sankaHQ/sanka-plugin /plugin install sanka@sanka /reload-plugins Start with /sakura:sakura for natural-language routing, or a specific /sakura:... skill ``` Enable auto-update from `/plugin` if you want Claude Code to pull future updates from GitHub. ### Cursor And Other Local MCP Clients Use `mcp.json` from this repository as the local MCP server config. It runs: ```text node ./vendor/mcp-remote/bundled-proxy.min.cjs https://mcp.sanka.com/mcp ``` Keep the repository files available on disk so the local proxy can run and read exact user-provided receipt paths for expense attachment upload. For clients that cannot run local commands, use `mcp.remote.json` or connect directly to `https://mcp.sanka.com/mcp`. That mode supports normal Sakura MCP tools but cannot read `local_file_path`; file uploads must provide `content_base64`. ## Use Examples: ```text $sakura:sakura Create an estimate from this HubSpot deal URL. $sakura:deal-to-estimate https://app.hubspot.com/contacts/.../record/0-3/... Preview the estimate and do not create it yet. $sakura:deal-to-estimate https://app.hubspot.com/contacts/.../record/0-3/... Create the estimate from this HubSpot deal. $sakura:list-deals Show recent deals. $sakura:create-expense Create an expense from this receipt. $sakura:refresh ``` For Claude Code, use `/sakura:sakura` as the general Sanka entrypoint when the user wants to say the request naturally. Use narrower skills like `/sakura:deal-to-estimate` when the workflow is already obvious. For HubSpot deal URLs, use the Sanka router or workflow skills when the outcome is a Sanka estimate, approval request, workflow run, or audit trail. HubSpot is only the source record; Sanka owns the business action. ## Refresh If Sanka says the plugin is outdated, the user should only need to answer "yes". User-facing prompt: ```text Sanka may be outdated. This action needs a newer Sanka workflow skill. Update Sanka? Reply "yes" and Codex will refresh Sanka and make the new Sanka skills available. ``` Codex can then run: ```bash ./scripts/refresh-codex-plugin.sh ``` After refresh, reload or reinstall Sanka in Codex and start a fresh thread from the Sakura chip or `$sakura:...`. Existing threads may keep an old MCP tool list. ## Packaging Codex loads this repository through `.agents/plugins/marketplace.json`, which points at `plugins/sanka` so the plugin source path is a real subdirectory. Claude Code continues to use the root `.claude-plugin` files with `source: "./"`. When changing root Codex files such as `.codex-plugin/`, `skills/`, `assets/`, `.mcp.json`, or `codex.mcp.json`, run: ```bash node scripts/sync-codex-package.mjs node scripts/sync-codex-package.mjs --check ``` ## Notes - Hosted MCP endpoint: `https://mcp.sanka.com/mcp` - Local MCP proxy: `node ./vendor/mcp-remote/bundled-proxy.min.cjs https://mcp.sanka.com/mcp` - Codex MCP server name: `sanka` - Local plugin clients should use the packaged proxy so expense attachment tools can accept exact `local_file_path` values. Remote-only MCP clients can use `mcp.remote.json` or connect to the hosted endpoint directly, but they cannot read local file paths. - Live Sanka work must use attached Sakura MCP tools. Do not substitute local Django shell, Postgres, repo files, or HubSpot MCP for Sanka actions. - If only `search_docs` / `execute` appear, refresh the plugin attachment or start a fresh plugin-attached thread. ## Translations - [English](./README.md) - [Japanese / 日本語](./i18n/README.jp.md)