View as Markdown↗

Use the Claude Code plugin

The Inttegro plugin combines the production MCP server with developer guidance, merchant workflows, and specialist agents. It does not fork Inttegro business logic or authorization policy.

What the plugin includes

Claude forms each command from the plugin namespace and the bundled skill name. The plugin is inttegro, so its skills use short local names such as /inttegro:checkout rather than repeating the brand on both sides of the namespace separator.

Eight developer skills

Skill	Best for
/inttegro:integration	Choose compatible API, SDK, Checkout, and MCP surfaces and implement the first complete workflow
/inttegro:best-practices	Authentication, money, idempotency, retries, pagination, privacy, and observability
/inttegro:checkout	Hosted Checkout, redirects, payment-state verification, buy links, and fulfillment boundaries
/inttegro:state-sync	Lookup, bounded polling, and reconciliation for changing resource state
/inttegro:testing	Contract, failure, idempotency, Checkout, and end-to-end test coverage
/inttegro:debug	Evidence-led diagnosis of API, SDK, Checkout, and MCP failures
/inttegro:upgrade	Safe SDK, generated-client, API-contract, Checkout, and MCP migrations
/inttegro:mcp	Remote MCP setup, authentication, capability handling, and MCP-powered applications

These also remain available as standalone skills with globally discoverable names such as inttegro-checkout on skills.sh. The shorter names apply only inside the namespaced plugin.

Twelve merchant workflows

Skill	Best for
/inttegro:collect-unpaid-orders	Find eligible unpaid orders and carry out only approved recovery actions
/inttegro:customer-care	Customer records, purchase activity, message status, and consented SMS
/inttegro:daily-brief	Numbers-first order, product, customer, balance, payout, and message summaries
/inttegro:files	File upload, processing status, sharing, revocation, and deletion
/inttegro:fulfill-and-close	Find paid incomplete orders, complete approved ones, and optionally send receipts
/inttegro:launch-offer	Set up a product and price, then publish or create a buy link as requested
/inttegro:message-templates	Draft, preview, publish, archive, and send reusable SMS or email templates
/inttegro:order-desk	Order investigation, creation, invoices, receipts, and compact status views
/inttegro:payment-refund	Masked payment selection, confirmed payment attempts, and exact line-item refunds
/inttegro:reconciliation	Balances, balance transactions, payouts, payout settings, and payment policy
/inttegro:resolve-customer-case	Investigate one customer issue and carry out the approved resolution
/inttegro:sell-by-link	Existing products, prices, hosted buy links, link lifecycle, and link delivery

Five 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
@inttegro:sales-closer	Moving an approved product or offer toward a completed sale
@inttegro:order-operations-manager	Resolving order blockers and advancing fulfillment work
@inttegro:customer-resolution-specialist	Investigating and resolving one customer case with approved actions

The two investigators are read-only. Outcome operators can prepare actions, but the same MCP authorization and confirmation controls apply before any change.

Install the plugin

Install the public marketplace and plugin:

claude plugin marketplace add inttegro/ai
claude plugin install inttegro@inttegro

Then in Claude Code:

1. Open /mcp, choose the Inttegro server, and complete sign-in.
2. Run /help and verify the twenty /inttegro:... skills.
3. Ask Claude to use one of the five @inttegro:... specialists.
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.

To validate a checkout of the public inttegro/ai repository directly, run:

npx -y @anthropic-ai/[email protected] plugin validate plugins/inttegro --strict
npx -y @anthropic-ai/[email protected] --plugin-dir ./plugins/inttegro

Try the plugin

Design an integration

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

Use /inttegro:integration to choose the right Inttegro integration surfaces and implement the first complete workflow. Use the exact design_integration MCP tool when available, then follow its returned agent_brief, required operations, Studio links, and test plan. 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: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:launch-offer. Create a draft service called “Meetup consultation,” add a GHS 350.00 price, publish it, 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: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 public AI repository contains the plugin source, validation scripts, marketplace metadata, and live OAuth client configuration. Directory review, publisher verification, complete host evaluation, and any final Anthropic approval 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.