Agent plugin and skill

The CashSDK agent bundle includes the remote MCP connection and an integration skill. The skill guides your agent through platform selection, catalog setup, entitlements, checkout and verification. It reads your actual setup checklist and release availability before recommending an SDK.

Download the plugin and skill and extract the cashsdk-agent directory. A SHA-256 checksum is available alongside the archive. The bundle contains no credentials.

Install in your client#

Claude Code#

Add the extracted directory as a local marketplace:

/plugin marketplace add /absolute/path/to/cashsdk-agent
/plugin install cashsdk@cashsdk-local

Restart your session if prompted. Open /mcp, select CashSDK and authenticate. Invoke /cashsdk:cashsdk to start guided setup. For a temporary session, use claude --plugin-dir /absolute/path/to/cashsdk-agent instead.

These are local installation instructions. CashSDK does not depend on a listing in a public plugin marketplace. See Claude Code's plugin documentation.

Codex#

In clients that support local plugin marketplaces, add the extracted directory and install CashSDK. The bundle includes the portable plugin manifest and Codex compatibility files. See OpenAI's plugin installation guide.

Recent Codex CLI versions can install the local plugin:

codex plugin marketplace add /absolute/path/to/cashsdk-agent
codex plugin add cashsdk@cashsdk-local

Complete browser sign-in when the client requests it. If your version has no plugin command, connect MCP directly:

codex mcp add cashsdk --url https://mcp.cashsdk.com/mcp
codex mcp login cashsdk

Copy the extracted skills/cashsdk directory into your project's .agents/skills/cashsdk. Restart your session and invoke $cashsdk. The skill and MCP server are installed separately in this fallback.

Cursor#

If your Cursor version accepts a local portable plugin, select the extracted directory. Otherwise merge this server into .cursor/mcp.json:

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

Copy skills/cashsdk into your project's .cursor/skills/cashsdk. Open MCP settings and connect CashSDK. See Cursor's MCP guide.

Choose the account and access#

Your client opens CashSDK in the browser. Sign in, search for your workspace, select all apps or a single app, and review the requested permissions. Workspace owners and administrators can approve access. Choose Deny access to cancel. Each client authorizes independently; do not copy a CLI access token into an editor configuration. You can revoke access in Settings, MCP.

The CashSDK CLI browser-login build also displays a verification code in the terminal. Confirm it matches the browser before approving. The browser shows Access granted only after the CLI exchanges the authorization code and saves its credentials. See Sign in with your browser.

Confirm the installation#

Ask your agent:

Use CashSDK to list my apps and available platforms. Inspect my selected app's
setup checklist, explain the remaining steps and verify installed SDK versions
before making changes.

A successful installation can call get_platform_catalog and list_apps. An app-limited connection should inspect its authorized app instead of listing the workspace. Adding a URL alone does not verify authentication.

Pick the right integration#

The skill checks the platform support matrix and live catalog for released packages, preview features and source-only integrations. A completed installation is not payment certification. Verify your actual sandbox purchase, webhook delivery, access update and refund behavior before enabling paid traffic.

Troubleshooting#

• No tools: enable the MCP connection and complete browser sign-in. Restart the client if it caches its tool list.
• No workspace: use an owner or administrator account in the intended workspace. Membership and app access are checked again when you approve.
• Access denied or expired: authenticate again. A setup token expires after 24 hours; prefer OAuth for daily use.
• Tools appear twice: remove the duplicate manual or plugin connection.
• CLI callback cannot open: run login on the same computer as the browser. For a headless machine, use a durable MCP token through cashsdk auth set.
• Checkout paid but access pending: inspect webhook delivery and the setup checklist. A browser return page alone does not grant an entitlement.

The bundle's skills/cashsdk/references directory includes integration and diagnostic runbooks your agent can read when needed.