Norce Config MCP — Tool Reference

This page documents the tools exposed by the Norce Config MCP Server. For setup and connection instructions, see Using the Norce Backend MCP Servers.

The Config MCP is a read-only server in this version. Write tools for creating and updating configuration are planned for a future release.

response_format parameter: Most tools accept a response_format parameter — either "markdown" (default, human-readable) or "json" (for programmatic use). This parameter is not listed individually under each tool.

A note on application IDs

All Config MCP tools require an application ID as input. In this version there is no tool to discover application IDs without one — the initial application ID must be known in advance and provided to the AI through your system prompt or explicitly at the start of a conversation.

Find your application ID in Norce Admin, or ask your Norce contact. Once you have one, norce_config_list_applications can retrieve the full list.

Tools

List Applications

norce_config_list_applications

Lists all applications (storefronts) configured for the client, with their IDs, names, URLs, and active status.

Use this tool as the starting point when you need to know which applications exist — for example before calling norce_config_get_application_overview, or to look up an application ID to use in other MCP servers.

Parameters

• applicationId — any valid application ID for the client. Used to identify the account; the tool returns all applications for that client.

Output

A list of applications with their IDs, names, URLs, and active status.

Get Client Overview

norce_config_get_client_overview

Returns a consolidated snapshot of the client's top-level configuration: all applications, client-level sales areas (including VAT codes), and currencies with exchange rates.

Use this tool as the first step in most support and validation workflows. It gives a broad picture of how the client is set up without needing to drill into individual applications or stores. It is also the right starting point when you need sales area IDs or VAT code IDs to use in the Pricing MCP.

Parameters

• applicationId — any valid application ID for the client.

Output

• applications — all storefronts with status and URLs.
• salesAreas — client-level sales areas, each with their VAT codes and IDs.
• currencies — active currencies with exchange rates.

Get Application Overview

norce_config_get_application_overview

Returns a consolidated configuration snapshot for a specific application: its details, the cultures, sales areas, and currencies active at the application level.

Use this tool when you need to know what a particular storefront exposes to end customers — which languages, markets, and currencies are active for that application specifically, as opposed to the broader client-level configuration.

Parameters

• applicationId — the ID of the application to inspect.

Output

• application — name, URL, and active status.
• cultures — languages active for this application, with primary flag.
• salesAreas — sales areas active at the application level.
• currencies — currencies available to this storefront.

List Stores

norce_config_list_stores

Lists all stores (physical or logical divisions) configured for the client, with their IDs, division codes, names, group classification, and active status.

Use this tool when you need to find a store ID before calling norce_config_get_store_overview or norce_config_check_store_setup. Store IDs and division codes returned here are also used as cross-references in the Inventory MCP and Pricing MCP.

Parameters

• applicationId — any valid application ID for the client.

Output

A list of stores with their IDs, division codes, names, group classification, and active status.

Get Store Overview

norce_config_get_store_overview

Returns a full configuration snapshot for a specific store: its details, linked warehouses, linked price lists, linked applications, and culture-specific names.

Use this tool when you need cross-reference data for other MCP servers — for example, to find which warehouse IDs are linked to a store (for the Inventory MCP) or which price list IDs are assigned to it (for the Pricing MCP). Also use it as a pre-read before any store association changes.

Parameters

• applicationId — any valid application ID for the client.
• storeId — the store ID from norce_config_list_stores.

Output

• warehouses — linked warehouses with IDs and location references.
• priceLists — linked price lists with IDs and codes.
• applications — storefronts this store is visible in.
• Store details including address, contact, open hours, and location coordinates.

Check Store Setup

norce_config_check_store_setup

Validates the configuration of a specific store and returns a structured diagnostic report with issues, warnings, and passed checks.

Use this tool during pre-deployment validation or when diagnosing a store that is behaving unexpectedly. It is more efficient than manually inspecting each setting — the tool checks all critical configuration points in one call and surfaces exactly what is missing or misconfigured.

Checks performed

• Store is active.
• Store has a division code (required for integration and availability lookups).
• At least one warehouse is linked.
• Each warehouse link has a location ID set (required for accurate inventory lookups).
• At least one price list is linked.
• At least one application is linked (required for storefront visibility).

Parameters

• applicationId — any valid application ID for the client.
• storeId — the store ID from norce_config_list_stores.

Output

A diagnostic report with issues[], warnings[], passed[], and an allOk boolean.

Typical workflows

Starting a support investigation

1. Call norce_config_get_client_overview to get a broad picture of the client's setup — applications, sales areas, and currencies in one call.
2. If the issue is related to a specific storefront, follow up with norce_config_get_application_overview for that application.
3. If the issue involves stock or pricing, use the warehouse IDs and price list IDs from norce_config_get_store_overview as input to the Inventory MCP and Pricing MCP.

Validating a store before go-live

1. Call norce_config_list_stores to find the store ID.
2. Call norce_config_check_store_setup with that store ID to run the full validation check.
3. If any issues are reported, call norce_config_get_store_overview to inspect the current state and identify what needs to be corrected.

Fetching reference data for other MCP servers

When a task requires IDs that other MCP servers need (price list codes, warehouse IDs, sales area IDs, VAT codes):

1. Call norce_config_get_client_overview for client-level sales areas and VAT codes.
2. Call norce_config_get_store_overview for the warehouse IDs and price list IDs linked to a specific store.

These IDs can then be passed directly to the Pricing MCP, Inventory MCP, or Supplier MCP.