Implement & Review with AI (MCP)
Fast Simon MCP — build and review the SDK with your AI assistant
The Fast Simon MCP server gives AI coding assistants authoritative, always-current knowledge of the Fast Simon JavaScript SDK — real method signatures pulled straight from the shipped type declarations, the documentation, and the reporting events — so your assistant can implement and review your Fast Simon integration accurately, right inside your own project.
It works with Claude Code and any other MCP-capable assistant (Cursor, Windsurf, Cline, …).
Add it once
claude mcp add --transport http fastsimon https://mcp.fastsimon.com/mcp
That's it — no account, no keys. The MCP is read-only: it never sees or stores your project
files (your assistant reads those locally), and it only serves content that is already public
— this documentation and the published fast-simon-sdk type declarations.
Implement
Ask in plain language, inside your storefront project:
Add a Fast Simon search results page to this theme.
Your assistant inspects your project, asks the MCP for the exact API shapes and the known-good recipe, and writes the code — adapted to your stack (Liquid theme, Hydrogen, headless, …). It loads the SDK from the CDN so your storefront always runs the latest published version.
Or start from a ready recipe — type / in Claude Code and pick one, e.g.
search-result-page, collection-page, upsell-and-cross-sell-recommendations,
visual-discovery-sample.
Review an existing integration
Run the review prompt (type / and choose it, or just ask):
/review-integration
Your assistant reads your existing Fast Simon code and audits it against the MCP — confirming method signatures, flagging any use of undocumented/internal APIs, and checking that every surface fires its required reporting events (a page that renders but reports nothing is an incomplete integration). Every finding is grounded in a tool result, not a guess.
What it knows
| Ask your assistant about… | The MCP provides |
|---|---|
| How to build a search / collection / recommendations / visual-discovery page | Searchable docs + ready recipes |
| The exact arguments a method takes | The authoritative signature from the SDK type declarations |
| Which events a surface must report | The event constants and payloads for that surface |
| Whether something is safe to use | A clear flag when a method/field is not part of the documented public API |
Because that knowledge is derived from the SDK and docs themselves, it stays correct as the SDK evolves — your assistant won't invent a method or a parameter that doesn't exist.