sanka-plugin
Sanka attaches Sanka's hosted MCP server to Codex and Claude Code. 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 attach the same hosted Sanka MCP server and the same $sanka:... skills.
Codex
Clone sankaHQ/sanka-plugin
Open the cloned repo in Codex
Restart Codex
Install Sanka from the Sanka marketplace
Start with the Sanka chip or a plain $sanka:... mention
Claude Code
/plugin marketplace add sankaHQ/sanka-plugin
/plugin install sanka@sanka
/reload-plugins
Start with /sanka:sanka for natural-language routing, or a specific /sanka:... skill
Enable auto-update from /plugin if you want Claude Code to pull future updates from GitHub.
Use
Examples:
$sanka:sanka Create an estimate from this HubSpot deal URL.
$sanka:deal-to-estimate https://app.hubspot.com/contacts/.../record/0-3/... Preview the estimate and do not create it yet.
$sanka:deal-to-estimate https://app.hubspot.com/contacts/.../record/0-3/... Create the estimate from this HubSpot deal.
$sanka:list-deals Show recent deals.
$sanka:create-expense Create an expense from this receipt.
$sanka:refresh
For Claude Code, use /sanka:sanka as the general Sanka entrypoint when the user wants to say the request naturally. Use narrower skills like /sanka: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:
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:
./scripts/refresh-codex-plugin.sh
After refresh, reload or reinstall Sanka in Codex and start a fresh thread from the Sanka chip or $sanka:.... 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/, or codex.mcp.json, run:
node scripts/sync-codex-package.mjs
node scripts/sync-codex-package.mjs --check
Notes
- Hosted MCP endpoint:
https://mcp.sanka.com/mcp
- Codex MCP server name:
sanka_plugin
- Live Sanka work must use attached hosted 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
