How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Crinkl Commerce logo. Crinkl Commerce MCP server connector.

Crinkl Commerce MCP Server

Verified commerce data and proof-backed shopper activation tools for agents.

ToolsTools
22
Last updatedLast Updated
CategoryCategory
All
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Crinkl Commerce MCP Server?

The Crinkl Commerce MCP server gives AI agents structured, permission-aware access to Crinkl Commerce through the Model Context Protocol. With 22 pre-built actions, agents can read, create, and update Crinkl Commerce data on behalf of authorized users.

Willow ships the Crinkl Commerce MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Crinkl Commerce is being used by every AI agent in your stack.

Tools

get-protocol-summary

Get a concise explanation of what Crinkl is and how the protocol works. Use this first if you have no prior context about Crinkl. Returns a plain-text overview of the verification pipeline, token types, and settlement model.

get-cumulative-gmv

Get cumulative Gross Merchandise Value (GMV) from the public cumulative feed. The live Crinkl site displays this live beta cumulative total on top of the finalized alpha base; provide startDate to bound the window explicitly. Returns a cryptographically signed token containing total USD cents, spend count, and computation timestamp.

get-daily-gmv

Get the signed GMV summary for a specific calendar date (UTC). Returns the verified spend count, total USD cents, and a cryptographic signature from the Crinkl authority. Each daily GMV token is independently verifiable using the issuer's Ed25519 public key.

get-trailing-gmv

Get a rolling N-day GMV trend summary. Returns daily verified GMV figures for the trailing window, enabling trend analysis of verified commerce volume. Each day's figure is backed by individually signed spend attestation tokens.

get-spend-signals

Get recent verified spend activity signals from the Crinkl network. Each signal represents a cryptographically attested receipt that has passed OCR extraction, store resolution, and hard verification. Signals include store name, category (e.g. Grocery & Supermarkets, Gas & Convenience), CBSA metro code, and spend amount — but no personally identifiable information. Use resolve-cbsa to convert CBSA codes to metro area names.

resolve-cbsa

Resolve a CBSA (Core Based Statistical Area) code to its metro area name. CBSA codes appear in spend signals and distribution data as 5-digit codes (e.g. '35620'). This tool converts them to human-readable names (e.g. '35620' → 'New York-Newark-Jersey City, NY-NJ'). Also handles non-metro codes like 'non-metro:US-TN'.

get-merchant-summary

Get aggregated merchant and category distribution across all verified spends. Shows top store brands, category breakdown (grocery, restaurant, gas, etc.), and spend concentration metrics. All data is derived from cryptographically verified receipt attestations.

get-spend-distribution

Get the geographic and category distribution of verified spends over a trailing window. Returns a breakdown by store category and CBSA (Core Based Statistical Area) metro code, enabling analysis of where and how verified commerce is distributed across the United States.

get-settlement-summary

Get Bitcoin settlement statistics for the Crinkl network. Returns the current BTC price used for reward calculations, sats-per-receipt rate, total Lightning Network payouts, total sats claimed by users, and wallets with balance. Crinkl settles receipt rewards in real Bitcoin via Lightning Network — this endpoint shows the on-chain settlement layer metrics.

get-gmv-inclusion-proof

Get a Merkle inclusion proof that a specific spend is included in a daily GMV total. Returns the spend leaf hash, sibling hashes for the Merkle path, and the GMV root hash. This cryptographic proof allows anyone to independently verify that a spend was counted in the reported GMV without trusting the server.

verify-reward-commitment

Verify a reward commitment token's cryptographic integrity. Checks that the reward Merkle tree is valid, the batch signature is authentic, and the reward amounts match the committed values. Reward commitments bind point/sat allocations to specific spends before payout, preventing retroactive manipulation.

verify-issued-gmv

Perform full end-to-end verification of a spend's inclusion in verified GMV. Accepts a spend attestation token, GMV token, GMV inclusion proof, and reward commitment token, then verifies: (1) spend token signature is valid, (2) GMV token signature is valid, (3) spend is in the GMV Merkle tree, (4) reward commitment is valid, (5) all spend IDs match across artifacts. This is the strongest possible verification — a single call that proves a receipt's entire journey from scan to settlement.

get-recent-issued-proofs

Get recently issued proof bundles that demonstrate end-to-end verifiability. Each bundle contains a spend attestation token, GMV inclusion proof, and reward commitment — everything needed to independently verify a receipt's journey from scan to Bitcoin settlement. These are real production proofs, not test data. Note: rewardCommitmentToken and batchAnchor may be null for recent spends because reward commitments are batched asynchronously (typically within hours). The spend token and GMV inclusion proof are always present and independently verifiable. Check the 'steps' array and 'ok' field for per-step verification results.

get-issuer-keys

Get the Crinkl authority's Ed25519 public key used to sign all attestation tokens. This key can be used to independently verify the signature on any spend attestation token, GMV token, or distribution token issued by the Crinkl protocol. The key is returned in base64 format.

get-reward-policy

Get the current Crinkl reward policy. Returns the active policy version, SHA-256 policy hash, reward parameters (referral bonuses, base points), category multipliers (grocery 1.5×, dining 1.5×, etc.), $CRINKL token holding tier multipliers, and the latest reserve checkpoint (BTC price, sats/receipt, coverage ratio). All values are deterministic — the policy hash covers the full parameter set. Updated daily.

get-agent-capabilities

Get Crinkl's canonical external agent capability catalog. Returns the live authority levels, the delegated agent capability set, the human-only governance controls, the approval boundaries, the current delegation model, and each gateway/MCP capability with its route, tool name, and source of truth.

get-vendors

Get the currently approved DKIM vendor domains exposed by the public agent endpoint. Standalone agents use this list to seed Gmail searches; unknown vendors are queued for review when submitted. No authentication required.

pair-agent

Start the human-authorized agent pairing flow. Generates a 4-character code that a human approves in the Crinkl PWA to authorize the agent. Returns the code and expiration time (10 minutes). No authentication required.

claim-api-key

Poll for the API key after the human approves the pairing code in the Crinkl PWA. Returns 202 while pending, 200 with the API key once approved, 410 if expired. Poll every 5 seconds. No authentication required.

verify-receipt

Preview DKIM verification of a billing email without creating a spend or earning sats. Returns extracted invoice data (vendor, amount, date, DKIM status). The full email is required because DKIM signatures are computed over the original RFC 2822 message bytes — the signature cannot be verified without them. The email is discarded after verification.

submit-receipt

Submit a DKIM-verified billing email to mint a spend token and earn sats. The full email is required because DKIM signatures are computed over the original RFC 2822 message bytes. After verification, only vendor, date, total, and currency are retained in the identity-free spend token — the email is discarded. Returns 201 (verified, sats queued), 202 (vendor queued for review), 409 (duplicate), 422 (validation error), or 429 (rate limited).

get-agent-me

Get your agent's submission count, earned sats, and wallet-level stats. Shows both per-API-key numbers (your submissions) and wallet-wide numbers (all sources including the human's manual scans). Returns satsPerReceipt (current rate).

Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Crinkl Commerce MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-crinkl-commerce": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/crinkl-commerce"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-crinkl-commerce": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/crinkl-commerce"
    }
  }
}

Claude Code

CLI
claude mcp add willow-crinkl-commerce --transport http https://<org>.mcp-s.com/mcp/mcp/crinkl-commerce

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/crinkl-commerce",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Crinkl Commerce

Willow adds the layer Crinkl Commerce and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Crinkl Commerce MCP Server FAQ

What is the Crinkl Commerce MCP server?

The Crinkl Commerce MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Crinkl Commerce data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Crinkl Commerce MCP server different from the official one?

The official Crinkl Commerce MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Crinkl Commerce MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Crinkl Commerce MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Crinkl Commerce, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Crinkl Commerce actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Crinkl Commerce MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Crinkl Commerce MCP locally, you'll see it.

What does the Crinkl Commerce MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Crinkl Commerce MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.