Crinkl Commerce MCP Server

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

Tools

Last Updated

Jun 14, 2026

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.

1 2 3

1–10 of 22 tools

Customize Tools

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

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.