Documentation/getting started

Connecting Claude

Free

Connect StoreMCP to Claude.ai, Claude Desktop, or Claude Code.

StoreMCP exposes a remote MCP server over HTTP — any Claude surface that supports MCP can connect to it.

Claude.ai (web)

  1. Go to claude.ai → Settings → Integrations
  2. Click Add custom integration
  3. Fill in:
    • Name: StoreMCP
    • URL: https://your-site.com/wp-json/storemcp/v1/mcp
    • Auth: Bearer token → paste your API key
  4. Click Add and enable the integration in a new chat

Within seconds, Claude will list the available tools. Start a chat and try:

"What's my store's total revenue this month?"

Claude Desktop

Claude Desktop uses a local claude_desktop_config.json. Add StoreMCP under mcpServers:

{
  "mcpServers": {
    "storemcp": {
      "url": "https://your-site.com/wp-json/storemcp/v1/mcp",
      "headers": {
        "Authorization": "Bearer sk_live_your_api_key"
      }
    }
  }
}

The file lives at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Restart Claude Desktop after saving.

Claude Code (CLI)

Add the server from your terminal:

claude mcp add storemcp \
  --transport http \
  --url https://your-site.com/wp-json/storemcp/v1/mcp \
  --header "Authorization: Bearer sk_live_your_api_key"

Then start Claude Code in any project and the tools will be available.

Verifying the connection

Ask Claude:

"What tools do you have from the storemcp server?"

You should see a list of tool names like store_mcp_list_products, store_mcp_get_site_info, etc.

Scope your keys

Give each integration its own key. Revoking Claude.ai later shouldn't break your Cursor integration.

Troubleshooting

  • Can't connect — Make sure the URL is HTTPS and your site is publicly reachable. Local-only sites won't work with Claude.ai.
  • Authentication failed — Re-copy the key from StoreMCP → API Keys. Keys start with sk_live_.
  • Tools missing — Check StoreMCP → Modules. Disabled modules won't expose tools.

See Connection errors for more.