Skip to content

Environment Setup

Complete these steps once when first onboarding to the MCP workflow. You do not need to repeat them for each project.

PrerequisiteInstall CommandNotes
Node.js v18+brew install nodeRequired by Shopify CLI and MCP servers
pnpmnpm install -g pnpmDefault package manager for all Dev MCP projects
Shopify CLIpnpm add -g @shopify/cliTheme development and deployment
Claude Codebrew install claude-codeAlso available via npm install -g @anthropic-ai/claude-code
Figma Desktop Appfigma.com/downloadsThe browser version does not work for MCP — you must use the desktop app
Entire.iobrew install entireio/tap/entireLinks Claude Code conversations to git commits for traceability

Add a system-wide environment variable to your shell configuration. If you don’t have a .zshrc file, create one:

Terminal window
touch ~/.zshrc && open ~/.zshrc

Add this line:

Terminal window
export DC_MCP_API_KEY="YOUR_API_KEY"

Replace YOUR_API_KEY with the key provided by your Technical Lead, then reload your shell:

Terminal window
source ~/.zshrc

The Dev MCP server should be initialised within your local Sites folder (e.g. ~/Sites). This allows the setup command to scaffold new projects directly.

Terminal window
cd ~/Sites

Create a .mcp.json file in your Sites folder:

{
"mcpServers": {
"dev-mcp": {
"type": "sse",
"url": "https://dev.mcp.dotcollective.com.au/sse",
"headers": {
"x-api-key": "${DC_MCP_API_KEY}"
}
}
}
}

Once initialised, running the setup command from within ~/Sites will automatically create new project directories with the full Skeleton theme, .mcp.json and all configuration files.

  1. Open the Figma desktop app and open a design file.
  2. Switch to Dev Mode (Shift+D or toggle in the bottom toolbar).
  3. In the right sidebar (Inspect panel), find the MCP server section.
  4. Click Enable desktop MCP server.
  5. Set Images to download (not local).

The server runs locally at http://127.0.0.1:3845/mcp. You need Figma open with a design file loaded and Dev Mode enabled whenever you start a Claude Code session that requires design context.

  • Ensure the Figma desktop app is open with a design file loaded
  • Confirm the MCP server is enabled in the Inspect panel
  • Restart both the Figma desktop app and Claude Code
  • Verify you have edit access to the Figma file (not just view access)

Entire.io links your Claude Code conversations to git commits, giving full traceability from code changes back to the AI session that produced them. It runs as a background hook — no workflow changes required.

Terminal window
brew install entireio/tap/entire

After installation, enable it in each project:

Terminal window
cd ~/Sites/<project-name>
entire enable

This creates an .entire/ directory in the project root. The settings.json file should be committed (shared project settings), while settings.local.json is gitignored (per-machine state).

When enabled, Entire.io runs a SessionStart hook that links the current Claude Code conversation to your next git commit. On commit, the conversation context is attached to the commit metadata — visible in the Entire.io dashboard and linkable from PR reviews.

After enabling, start a new Claude Code session. You should see a startup message:

Powered by Entire:
This conversation will be linked to your next commit.

If this message does not appear, check that entire --version runs successfully and re-run entire enable.

AppPurpose
WarpModern terminal with AI integration — ideal for managing multiple Claude Code sessions and split panes
Zed or VS CodeIDE for reviewing and browsing files outside of Claude Code. Either is fine — use whichever you prefer