Deutsche Version

Back to overview

Shopware Admin: Configuration

This documentation always describes the current state of the main branch.

Environment variables

Values come from the process environment or from the .env file (search order see Installation). A template ships as .env.example in the repository. Lines starting with # are comments, values may be wrapped in single or double quotes.

Required

Optional

WIKIJS_BASE_URL and the three CACHE_TTL_* variables are read and validated at startup (valid URL, value greater than 0) but no service uses them afterwards. Cache lifetimes are fixed in the code, see Technical details. The wiki hook always yields wikiUrl: null in content results.

At startup a missing HTTPS scheme in SHOPWARE_URL is only reported as a warning on stderr. The server also runs with http:// but then sends the credentials unencrypted. No warning is printed for localhost and 127.0.0.1.

Set up the Shopware integration

1. In the Shopware admin create a new integration under Settings > System > Integrations.
2. Copy client ID and client secret into the .env.
3. Give the integration the permissions for the areas you want to use.

The server signs in with the OAuth2 client credentials grant (POST /api/oauth/token). These are the entities it addresses per tool area:

The .env.example file names only part of these permissions. The repository contains no permission check: whatever the integration may do, the server may do. Grant only the permissions of the areas you need and use separate integrations for test and production.

Content profiles

The tools product_generate_content, product_generate_seo, variant_generate_content and category_generate_content produce instructions for Claude. Tone, form of address, structure and target audience come from content profiles that you define in a JSON file.

Search order

1. CONTENT_PROFILES_PATH, if set.
2. ~/.claude/mcp-servers/shopwareadmin/content-profiles.json, if present.
3. ./content-profiles.json in the working directory.

If the server finds no file at the resolved location it uses the built-in profiles and writes a note to the log. This also applies when CONTENT_PROFILES_PATH points to a missing file. An existing but invalid file prevents startup, with one error message per faulty field.

Structure

{
  "language": "de",
  "defaultProfile": "creative",
  "profiles": {
    "creative": {
      "tonality": "Persoenlich, warm, emotional",
      "addressing": "du",
      "structure": ["Emotionaler Einstieg (Frage/Anekdote)", "Was ist es?", "Technische Details (Format, Groesse)", "Anwendungstipps"],
      "targetAudience": "Hobbybastler, Kreative, DIY-Enthusiasten",
      "exampleIntro": "Was waere denn Ostern ohne den Osterhasen?",
      "includeSnippets": false
    }
  },
  "categoryMapping": {
    "Stickdateien": "creative"
  }
}

Built-in profiles

Without a file the profiles creative (address du, default) and software (address Sie, with snippets) apply. The category mapping is Software to software and Stickdateien, Genaehtes and 3D-Druck to creative. These are the values of the author's shop.

Style detection

• The server takes the product's first category and its breadcrumb (path from the root).
• Each path segment is compared exactly, case-sensitive, against the keys in categoryMapping. The first hit counted from the root wins.
• Without a hit or without a category defaultProfile applies.
• The style parameter overrides detection. An unknown name leads to INVALID_INPUT with the list of available profiles.
• variant_generate_content has no style parameter and always detects the style automatically.

Snippets

With includeSnippets: true the server queries the mmd-product-snippet entity. It comes from a Shopware plugin for product text snippets that must be installed in the shop. Without that plugin the query fails with an API error, and so does the snippet_list tool.