MCP tools, scopes and permissions

Access has three parts: the administrator enables an MCP tool group, the API client has the required scopes, and the operation targets an assigned shop. Enabling a group alone does not authorize its tools. NetSeller’s API still validates every operation.

Available areas

The following is an overview. Each exposed tool describes its exact inputs and required scopes; some tools accept alternative scopes or require several together.

Tool group	Purpose	Relevant API scopes
Orientation	Assigned shops, languages, currencies and tax settings	settings:read
Catalog read	Products, categories, variants, media and catalog definitions	Normally catalog:read; some discovery/media operations accept media scopes
Catalog write	Create and edit catalog data, assignments and imports	catalog:write; media operations use media:write, inventory adjustments use inventory:write
Checkout	Carts, items, addresses, shipping/payment selection and order submission	checkout:write
Orders read / write	Order history and details / status, refunds, documents, communications and shipments	orders:read / orders:write
Customers read / write	Customers, companies, addresses, shop registrations and memberships	customers:read / customers:write
Shop configuration read / write	Shop settings, theme settings, pages, homepage, footer, branding and redirects	settings:read or content:read / settings:write or content:write, depending on the tool
Marketing read / write	Coupons, vouchers, balances, price actions and abandoned-cart information	marketing:read / marketing:write
Webhooks read / write	Event registry, subscriptions and delivery history / subscription changes, secret rotation and replay	webhooks:read / webhooks:write

Read and write groups are separately configurable where shown. By default, MCP itself is disabled; orientation and catalog read are preselected, while the other groups are disabled. Existing installations may have different saved settings.

Choose access for the task

For product browsing, enable orientation and catalog read, grant settings:read and catalog:read, and assign the intended shops. For product editing, additionally enable catalog write and grant catalog:write. Media uploads and stock adjustments need their own scopes.

A write scope does not automatically include the corresponding read scope. Most editing workflows need both because they read the current resource before changing it.

Shop assignments constrain access; they do not turn shared catalog records into independent per-shop copies. Distinguish shared product data from shop-specific assignments and overrides before editing. The tool description and Commerce API reference describe each operation’s scope.

Discover tools and inputs

Refresh the tool list after access changes. Use the tool’s current input schema for required arguments, allowed values and limits. With catalog read enabled, netseller_get_catalog_capabilities reports supported catalog operations; it accepts one of catalog:read, catalog:write, media:read or media:write.

Use discovery tools for IDs and definitions instead of inventing them. For example, netseller_list_shop_custom_field_definitions requires settings:read and the shop-configuration read group. Only submit connector-visible custom-field keys returned for the target entity and shop.

MCP exposes specific operations, not arbitrary SQL or an unrestricted API proxy. A natural-language instruction still results in real operations: order submission, communications, refunds and other writes can have external effects. Use a development shop with fictitious data for examples.