Use the Claude Code plugin

The Inttegro plugin combines the production MCP server with merchant workflow guidance and read-only specialists. It does not fork Commerce business logic or authorization policy.

What the plugin includes

Seven Inttegro workflows

Skill	Best for
/inttegro:inttegro-integration-builder	SDK, checkout, API-operation, implementation, and end-to-end test planning through design_integration
/inttegro:inttegro-daily-brief	Numbers-first order, product, customer, and balance summaries
/inttegro:inttegro-order-desk	Order investigation, creation, invoices, receipts, and compact status views
/inttegro:inttegro-payment-refund	Masked payment selection, confirmed payment attempts, and exact line-item refunds
/inttegro:inttegro-sell-by-link	Products, prices, hosted buy links, link lifecycle, and link delivery
/inttegro:inttegro-customer-care	Customer records, purchase activity, message status, and consented SMS
/inttegro:inttegro-reconciliation	Balances, balance transactions, payouts, payout settings, and payment policy

Two read-only specialist agents

Agent	Best for
@inttegro:commerce-analyst	Multi-source operating briefs, analytics, and reconciliation
@inttegro:customer-journey-investigator	Tracing explicit order, customer, product, price, link, and message relationships

The specialist agents have only read tools. Any follow-up action returns to the main conversation for explicit confirmation.

Load the development plugin

From the Commerce repository root:

npx -y @anthropic-ai/claude-code@latest plugin validate plugins/inttegro --strict
npx -y @anthropic-ai/claude-code@latest --plugin-dir ./plugins/inttegro

Then in Claude Code:

1. Open /mcp, choose the Inttegro server, and complete sign-in.
2. Run /help and verify the seven /inttegro:... skills.
3. Ask Claude to use one of the two @inttegro:... specialists for a read-only investigation.
4. After changing plugin components, run /reload-plugins.

The plugin packages a public PKCE client and fixed localhost callback. Users authenticate directly with Inttegro; the plugin does not contain or require a client secret.

The repository also contains a local Claude marketplace manifest. Once that marketplace is hosted, users can install inttegro@inttegro instead of loading a checkout with --plugin-dir.

Try the plugin

Design an integration

Start here when Claude Code will build or extend the application itself:

Use /inttegro:inttegro-integration-builder to take me through the Inttegro integration decisions. Start with the exact design_integration MCP tool. When the architecture is settled, use the returned agent_brief, required operations, Studio links, and test plan to implement the integration. Do not ask me to paste an API key.

This replaces the initial manual work of choosing an SDK, finding the relevant API guides, and assembling a safe test sequence. Review the design_integration guide before giving Claude repository access or implementation authority.

Daily operating brief

Use /inttegro:inttegro-daily-brief. Show our 30-day order and product performance in GHS, including exact familiar-unit values and chart data. Add current balances and identify no more than three operational follow-ups. Do not estimate missing metrics.

Customer journey investigation

Ask @inttegro:customer-journey-investigator to trace order <ORDER_ID> through only the customer, product, price, buy-link, and message IDs explicitly returned by Inttegro. Give me an evidence timeline and unresolved gaps. Make no changes.

Sell by link

Use /inttegro:inttegro-sell-by-link. Create a draft service called “Meetup consultation,” add a GHS 350.00 price, create a single-use buy link for one unit, and send it to customer <CUSTOMER_ID>. Confirm every action separately and report each authoritative result.

Take payment or create a refund

Use /inttegro:inttegro-payment-refund for order <ORDER_ID>. If I choose payment, show only masked saved methods and keep new payment details in secure Inttegro Checkout. If I choose refund, guide me through the affected lines, exact amount per line, optional line reasons, and required overall reason. Preserve every MCP confirmation and reconcile the final status.

Presentation behavior

Compatible hosts can request portable MCP Apps cards for individual products, orders, analytics, product catalogs, and buy links. If the host does not support those views, the plugin falls back to exact structured results, concise text, Flint chart specifications, and optional PNG charts. UI support never changes the underlying data or authorization boundary.

Publication boundary

The repository contains the plugin source, validation inputs, golden prompts, marketplace metadata, and live OAuth client configuration. Public marketplace hosting, reviewer accounts, publisher verification, complete host evaluation, and final Anthropic submission remain external release steps.

See the design_integration guide for the integration-planning workflow, the tool catalog for the exact server surface, and merchant workflows for host-independent examples.