Claude Code + wmcp.sh: A 10-Minute Integration Tutorial

How to give Anthropic’s terminal agent dynamic web-shopping capabilities and OpenAPI tool-calling in under ten minutes.

Giving Claude Code a Real Browser Interface

When Anthropic launched Claude Code, it immediately became the tool of choice for terminal-first developers. It’s blazingly fast, runs completely local on your machine, handles complex codebase-wide refactors, and edits files directly.

But out of the box, Claude Code is trapped inside your local terminal.

If you ask it to "Check the current price of Allbirds Wool Runners in size 10" or "Pull the latest API schema from our staging payment server," it hits a brick wall. It lacks a browser interface, has no concept of public storefronts, and cannot map remote REST APIs dynamically to tools.

To solve this, we connect Claude Code to the Model Context Protocol (MCP) using the global dynamic gateway—wmcp.sh.

In this tutorial, we will walk step-by-step through configuring your local Claude Code terminal to dynamically map storefront checkouts (via Shopify) and arbitrary SaaS APIs (via OpenAPI specs) into tools in under ten minutes. No compilation, no static codegen, and no local server overhead.

How Claude Code Resolves MCP Configuration

Claude Code handles MCP servers differently than the graphical Claude Desktop application. While the desktop app relies exclusively on a single claude_desktop_config.json file, Claude Code parses two distinct configuration Scopes:

1. Global Scope (~/.claude.json): User-wide configuration. Any MCP server registered here is loaded by Claude Code across all terminal directories and projects.
2. Project Scope (./.mcp.json): Directory-specific configuration. Placed in a project's root folder, it dictates specific local APIs or database connections that should be isolated to that workspace.

You can configure these servers either by editing the JSON files directly, or by utilizing Claude Code's native claude mcp terminal helper command.

We will use the Global Scope configuration so that your terminal agent has web-shopping and OpenAPI-mapping capabilities active wherever you are running terminal loops.

Step 1: Locating and Editing the Configuration File

First, open your terminal and locate your global Claude configuration. Under macOS and Linux, this is stored at ~/.claude.json.

If the file does not exist, you can create it manually, or run claude mcp list to let Claude Code initialize the folder structure for you.

Open the file in your preferred editor (e.g. VS Code, Vim, or Nano) by running:

code ~/.claude.json

Inside, you will see a structured JSON configuration. We will append the mcpServers block to declare the hosted wmcp.sh server.

Step 2: Adding the wmcp.sh Configuration Block

To link Claude Code to the dynamic gateway, add the following configuration block to your mcpServers list.

We will expose the wmcp.sh HTTP-transport gateway directly. This ensures that when Claude Code starts up, it communicates with the stateless gateway to resolve tools dynamically:

{
  "mcpServers": {
    "wmcp-gateway": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch"
      ],
      "env": {
        "WMCP_API_KEY": "your_pro_api_key_here",
        "WMCP_GATEWAY_URL": "https://wmcp.sh/api/v1"
      }
    }
  }
}

Note: Replace your_pro_api_key_here with your active Pro key from the wmcp.sh dashboard, or leave it blank to run under the anonymous free tier (100 reads/day).

Option B: Using the CLI helper command

Alternatively, if you prefer utilizing the command line instead of editing JSON files, you can run this single command inside your terminal:

claude mcp add wmcp-gateway -- npx -y @modelcontextprotocol/server-fetch

This will automatically populate your ~/.claude.json file with the correct pathing and arguments.

Step 3: Verifying the Connection

Once you have saved the configuration file, restart Claude Code. If you are currently in an active session, type /exit and restart the CLI from your terminal:

claude

During initialization, Claude Code will parse your ~/.claude.json file, connect to the configured servers, and log the status. You can verify that the gateway is loaded successfully by running:

claude mcp list

You should see wmcp-gateway listed under active servers with a status of CONNECTED or READY.

Step 4: Running Your First Shopping and API Actions

Now that your terminal agent is connected, let's put it to work! You can immediately ask Claude Code to execute shopper-side actions on any public Shopify storefront.

Try asking:

"Check the variant stock of Allbirds Wool Runners at https://www.allbirds.com/products/mens-wool-runners and add size 10 to my cart."

Claude Code will:

1. Intercept the URL and detect that it is a public storefront.
2. Route a background request via the wmcp-gateway tool block.
3. Receive a standardized tool array in under 100ms containing get_price, check_stock, and add_to_cart.
4. Invoke add_to_cart and return a real cart checkout token directly to your terminal.

[Visual: Terminal screenshot showing Claude Code successfully calling the Allbirds add_to_cart tool and outputting a live Checkout URL]

Dynamic OpenAPI Mapping

You can also ask Claude Code to dynamically map remote REST APIs on the fly. Try running:

"I need you to interact with the PetStore API. Read the OpenAPI spec at https://petstore3.swagger.io/api/v3/openapi.json, list the endpoints, and find a pet with status 'available'."

Claude Code will automatically hit the spec URL, parse the entire Swagger path tree in memory, register every endpoint as a parameterized tool, execute the GET /pet/findByStatus query, and output the resulting JSON—all without generating a single line of typescript or compile boilerplate!

10 Minutes to Infinite Agent Capabilities

By taking ten minutes to configure your local terminal agent, you have expanded its capabilities exponentially. Instead of being isolated inside your local file system, Claude Code can now act as a consumer browsing millions of merchant storefronts and orchestrate actions across arbitrary SaaS platforms on demand.

Unit efficiency and zero-setup setups are the primary drivers of developer adoption. Stop writing custom scrapers for every integration—link Claude Code to wmcp.sh today, and let dynamic tool-mapping handle the heavy lifting.