---
title: "Use the Claude Code plugin"
description: "Load Inttegro developer skills, merchant workflows, and specialist agents in Claude Code."
canonical: "https://studio.inttegro.com/inttegro-mcp/claude-code"
format: inttegro-machine-docs/v1
language: "C#"
sdk_version: "v10.3.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/csharp/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 524
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["design_integration"]
estimated_tokens: 2951
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Load Inttegro developer skills, merchant workflows, and specialist agents in Claude Code. This C# representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Use the Claude Code plugin?

Use this MCP document when an authenticated AI client needs governed Inttegro context, guidance, presentation, or operations.

#### Q2. What is authoritative on this page?

The documented MCP catalog defines available abilities and confirmation boundaries. For live state, the structured tool result is authoritative; presentation output is only a rendering of that result.

#### Q3. What page-specific constraint matters most?

Read operations do not authorize mutations. Actions retain their exact confirmation requirements, and payment credentials or OTP must stay in secure Checkout.

#### Q4. Can Inttegro MCP materially help with this task?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `design_integration`; their exact roles and boundaries are listed below.

#### Q5. How should the reader verify the answer and continue?

Preserve the structured tool result, distinguish bounded lists from complete analytics, and reconcile asynchronous actions through an authoritative read. Continue with [merchant workflows](https://studio.inttegro.com/machine/csharp/inttegro-mcp/workflows.md) and [tool catalog](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`design_integration`](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md#design_integration) — read-only integration guidance. Elicits the integration goal, AI app builder, server runtime, SDK preference, and checkout approach, then returns a platform-aware build and test plan without accepting credentials.

## Document content

# 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](https://skills.sh/inttegro/ai). 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:

```bash
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`](https://github.com/inttegro/ai) repository directly, run:

```bash
npx -y @anthropic-ai/claude-code@2.1.269 plugin validate plugins/inttegro --strict
npx -y @anthropic-ai/claude-code@2.1.269 --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](https://studio.inttegro.com/machine/csharp/inttegro-mcp/design-integration.md) 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](https://studio.inttegro.com/machine/csharp/inttegro-mcp/design-integration.md) for the integration-planning workflow, the [tool catalog](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md) for the exact server surface, and [merchant workflows](https://studio.inttegro.com/machine/csharp/inttegro-mcp/workflows.md) for host-independent examples.