Use the Claude Code plugin
The Inttegro Commerce plugin combines the production MCP server with merchant workflow guidance and read-only specialists. It does not fork Commerce business logic or authorization policy.
Direct Claude Code connections with a restricted API key are documented in Connect an MCP client. Interactive plugin users are intended to authenticate through OAuth instead of supplying an API key.
What the plugin includes
Five merchant workflows
| Skill | Best for |
|---|---|
/inttegro-commerce:inttegro-daily-brief | Numbers-first order, product, customer, and balance summaries |
/inttegro-commerce:inttegro-order-desk | Order investigation, creation, invoices, receipts, and compact status views |
/inttegro-commerce:inttegro-sell-by-link | Products, prices, hosted buy links, link lifecycle, and link delivery |
/inttegro-commerce:inttegro-customer-care | Customer records, purchase activity, message status, and consented SMS |
/inttegro-commerce:inttegro-reconciliation | Balances, balance transactions, payouts, payout settings, and payment policy |
Two read-only specialist agents
| Agent | Best for |
|---|---|
@inttegro-commerce:commerce-analyst | Multi-source operating briefs, analytics, and reconciliation |
@inttegro-commerce: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-commerce --strict
npx -y @anthropic-ai/claude-code@latest --plugin-dir ./plugins/inttegro-commerce
Then in Claude Code:
- Open
/mcp, choose the Inttegro server, and complete sign-in. - Run
/helpand verify the five/inttegro-commerce:...skills. - Ask Claude to use one of the two
@inttegro-commerce:...specialists for a read-only investigation. - After changing plugin components, run
/reload-plugins.
The repository also contains a local Claude marketplace manifest. Once that marketplace is hosted, users can install inttegro-commerce@inttegro instead of loading a checkout with --plugin-dir.
Authentication status
Interactive Claude Code installation depends on the MCP server advertising an OAuth authorization server in /.well-known/oauth-protected-resource. Without that metadata, Claude Code can discover that authentication is required but cannot complete merchant account linking.
Interactive OAuth linking is not yet enabled on the production endpoint. Use the direct restricted API-key connection for customer-controlled testing until Inttegro announces that plugin account linking is ready.
Do not add a static Authorization header to the interactive plugin configuration: a configured static header disables Claude Code's OAuth fallback when the server rejects that credential. For an intentional customer-controlled workload, use the separate restricted API-key connection.
Try the plugin
Daily operating brief
Use
/inttegro-commerce:inttegro-daily-brief. Show our 30-day order and product performance in GHS, including exact minor-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-commerce:customer-journey-investigatorto 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-commerce: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.
Presentation behavior
Compatible hosts can request portable MCP Apps cards for 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, and marketplace metadata. Public marketplace hosting, OAuth consent configuration, policy pages, reviewer accounts, publisher verification, and final Anthropic submission are external release steps and are not represented as complete until verified.
See the tool catalog for the exact server surface and merchant workflows for host-independent examples.