Dropins MCP
Dropins MCP is a free Model Context Protocol (MCP) server for Cursor, VS Code, Claude Code, and Claude Desktop. It indexes drop-in source code — both B2C and B2B — so your AI editor gets current slots, events, containers, API functions, and design tokens, instead of relying on outdated training data.
Prerequisites
Section titled “Prerequisites”Before installing the Dropins MCP server, make sure you have the following:
- Node.js 18 or later (
node -vto confirm) - An AI editor that supports MCP servers: Cursor , VS Code with GitHub Copilot , Claude Code , or Claude Desktop
Installation
Section titled “Installation”Configure the Dropins MCP server in your editor and verify the connection.
-
Add the server to your editor configuration. Open the tab for your editor and paste the snippet into the config file shown. If you use the Claude Code extension in VS Code, choose the Claude Code tab, rather than VS Code (Copilot), which is for VS Code’s built-in MCP support through GitHub Copilot.
Add to
~/.cursor/mcp.jsonfor all projects, or.cursor/mcp.jsoninside a specific project:{"mcpServers": {"dropins": {"command": "npx","args": ["@dropins/mcp"]}}}Add to
.vscode/mcp.jsoninside your project:{"servers": {"dropins": {"type": "stdio","command": "npx","args": ["@dropins/mcp"]}}}Add to
.mcp.jsonat your project root (this applies to both the Claude Code VS Code extension and the Claude Code CLI):{"mcpServers": {"dropins": {"type": "stdio","command": "npx","args": ["@dropins/mcp"]}}}Claude Code uses your terminal’s PATH, so
npxworks without a global install.To auto-approve the server without a prompt each session, add the following to
.claude/settings.jsonin your project:{"enableAllProjectMcpServers": true}The config file lives outside your project:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
In Claude Desktop, choose Settings, open Developer, then click Edit Config to create or open that file.
Add to
claude_desktop_config.json:{"mcpServers": {"dropins": {"command": "dropins-mcp"}}}Claude Desktop is a desktop app, not a terminal, so it doesn’t read your shell’s PATH. Commands such as
npxmight not be found when Claude Desktop tries to start the server. A global install puts the binary in a system location Claude Desktop can reach:npm install -g @dropins/mcpIf you use
nvm, the binary lands in a version-specific folder that isn’t on the system PATH. Run this in your terminal to find the full path:which dropins-mcpThen replace
dropins-mcpin the config with that absolute path. For example:/Users/yourname/.nvm/versions/node/v20.11.0/bin/dropins-mcp - macOS:
-
Restart your editor. When the server loads,
dropinsappears in your editor’s MCP server list. -
Verify the connection. Ask your AI editor:
“Use the dropins MCP — what slots does the CartSummaryList container have?”
If your AI editor returns a list of slot names with context types, the MCP server is connected and working.
If
dropinsdoesn’t appear in your editor’s MCP list, or your editor can’t answer the question, open your editor’s MCP logs and confirm thatnpx @dropins/mcpruns without errors in a terminal outside the editor.
Example prompts
Section titled “Example prompts”The MCP works best when you ask specific questions about your project. For example:
- “What events does the checkout drop-in emit when a payment method is selected?”
- “Create a block that combines CartSummaryList and OrderConfirmation”
- “Are there any stale containers or removed APIs in my commerce-cart block?”
- “What GraphQL mutation does checkout use to place an order?”
- “Generate a slot implementation that adds a loyalty points badge next to the cart line item price”
- “Am I using the latest drop-in versions?”
- “What CSS design tokens control button colors?”
Enable documentation search (optional)
Section titled “Enable documentation search (optional)”The search_commerce_docs tool searches Adobe Commerce documentation on Adobe’s servers using the Adobe I/O command-line interface (CLI). Without it, the MCP still answers drop-in questions using search_docs, which searches a local copy of the documentation included with the server.
To sign in and enable remote documentation search, install the Adobe I/O CLI and log in once:
npm install -g @adobe/aio-cliaio auth login