mcpField
M
mercadopago-integration

mercadopago-integration

github.com/martinacostadevDevelopment8217 installsUpdated 34w ago
Repository

About mercadopago-integration

mercadopago-integration is a safety-scoped skill for developers planning and scaffolding payment integrations. It supports provider-agnostic contracts and mock flows, but excludes live provider operations.

Key features

  1. 01Define provider-agnostic checkout contracts
  2. 02Create mock adapters with deterministic fake IDs
  3. 03Build UI states and polling against mock endpoints
  4. 04Recommend order schemas and status transitions
  5. 05Add validation and idempotency patterns
  6. 06Prepare a security handoff for future rollout

Use cases

  1. 01Scaffold mock API routes for a payment flow
  2. 02Design checkout states from pending to final
  3. 03Test idempotency and status transitions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/martinacostadev/mercadopago-integration --skill mercadopago-integration

After installing, type/mercadopago-integrationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

SECURITY.md
assets/
migration.sql
references/
client-implementation.md
countries.md
database-postgresql.md
database-prisma.md
database-supabase.md
server-implementation.md
testing.md
troubleshooting.md
usage-examples.md

Details

From the project README

Provider Integration (Non-Executing Safe Mode)

This skill is limited to planning and scaffolding. It does not provide instructions or code for live provider execution.

Mandatory Safety Boundaries

Never produce or modify code that:

  • installs or imports an external provider SDK
  • reads or writes provider credentials/secrets
  • creates live checkout sessions
  • processes provider callbacks
  • performs live transaction state changes

If a user asks for any of the above, stop and provide a security handoff note.

Allowed Scope

  1. Define provider-agnostic contracts (CheckoutProvider interfaces).
  2. Create mock server adapters with deterministic fake IDs.
  3. Implement UI states and polling logic against mock status endpoints.
  4. Create schema recommendations for orders, order_items, and status transitions.
  5. Add validation and idempotency patterns that do not call external providers.

Suggested Workflow

  1. Explore project structure and detect framework/database patterns.
  2. Propose minimal provider interface and mock implementation.
  3. Add safe API routes backed by mock storage.
  4. Build client flow (start checkout -> pending -> final status).
  5. Add tests covering idempotency and status transitions.

Output Style

  • Keep generated code provider-agnostic.
  • Use clear TODO markers where a real provider would later be integrated.
  • Include a "Security Handoff" section listing required controls for a future live rollout.

References

  • references/server-implementation.md
  • references/client-implementation.md
  • references/testing.md
  • references/troubleshooting.md
  • references/usage-examples.md
  • SECURITY.md — accepted risk documentation (W009)

Comments

Markdown supported