Jun 30, 2025 | 4 minute read

Dev MCP server: Ship Storefronts in Minutes

Building a storefront should be as simple as importing a component—not wrestling with endless REST endpoints. Connect any MCP-compatible IDE agent to our Dev MCP server and instantly unlock authenticated product search, seamless cart management, and flexible multi-method checkout. What used to take hours of API integration now happens in seconds.

Quick start (Cursor IDE)

Follow these steps to point Cursor at the Elastic Path MCP registry:

Locate — In Cursor open Settings → MCP → + Add new global MCP server. Cursor creates (or reveals) .cursor/mcp.json in your workspace. You can also create the file manually inside the .cursor folder.
Paste the server block — mcp-remote is a lightweight relay that speaks the MCP wire protocol over SSE. Replace or merge the contents with:
Save and trigger the agent — Ask your Cursor agent a question; it will launch mcp-remote, stream the request to Elastic Path, and pipe the response back into your editor.
Using another IDE? — In VS Code, Replit, or JetBrains, point the agent plug‑in at https://dev-agent.elasticpath.com/.well-known/mcp.json and supply the same beta key.

Closed beta access

The Dev MCP server is currently in closed beta. Contact your Elastic Path representative (or email [email protected]) to request an invite and receive your beta key.

Example agent call

{
 "tool": "elasticPathDevDocs",
 "args": {
 "prompt": "Generate a responsive product‑grid page with category filters, add‑to‑cart buttons, and a header subtotal",
 "host": "https://euwest.api.elasticpath.com",
 "codeStyle": "typescript",
 "framework": "nextjs"
 }
}

The agent returns a TypeScript + Next.js starter: a product‑listing page wired to Elastic Path search APIs, React hooks for cart state, and subtotal display logic—ready to run with npm run dev. Adjust framework or codeStyle (e.g., "react", "javascript") to fit your stack, or omit both to accept defaults.

Why you need it

Scaffold storefronts in minutes. Tell your agent to add a “product grid” or drop in a “cart drawer,” and the Dev MCP server supplies a production‑ready scaffold already wired to Elastic Path APIs—turning days of boilerplate into minutes of polish.
Built‑in commerce expertise. Every response bundles docs, sample REST calls, and coding patterns vetted by Elastic Path engineers, so you follow proven headless‑commerce practices without hunting through guides.
Code that matches your repo. The agent re‑styles snippets on the fly to fit your chosen framework, file structure, and TypeScript/JavaScript conventions.
Works in any agent‑aware IDE. The same MCP registry integrates with Cursor, VS Code, JetBrains, or any IDE that speaks MCP—choose the environment you prefer.

How it works

Discovery – Your IDE agent pulls https://dev-agent.elasticpath.com/.well-known/mcp.json, which currently advertises the tool elasticPathDocs (additional tools will appear over time) and its input schema.
Auth token – The mcp-remote relay adds the bearer token defined in mcp.json to every request.
Request – When you ask for help (e.g., “Generate a product grid”), the agent packages the prompt and options (framework, codeStyle, etc.) and streams the call to the server over Server‑Sent Events (SSE).
Generation – The server selects the best‑fit recipe from its curated library of snippets, API calls, and docs, then returns a JSON payload. The ide agent can insert the snippet as‑is or context‑aware‑rewrite it to match your project’s style, structure, and naming conventions.
Iterate – Follow‑up questions ("add cart context", "localise currency") trigger new tool calls — no context reset.