Connect an MCP client to NetSeller

MCP (Model Context Protocol) lets an AI assistant call NetSeller tools to read or change shop data. You need a client supporting Streamable HTTP, your installation’s HTTPS address, and an API key. The administrator controls which operations are available.

1. Prepare access in NetSeller

1. Open Settings → Integrations → MCP server with an administrator allowed to edit this integration.
2. Enable Allow MCP connections and the required tool groups. Start with orientation for a connection check; add catalog read for product lookups.
3. Save and copy the MCP server address shown on this page.
4. Under Settings → API clients, create or select an active API client, assign the intended shops and grant the required scopes. The connection check needs settings:read; product lookups also need catalog:read.
5. Obtain its API key through the administrator. Use a dedicated API client so access can be managed separately.

The endpoint has this form:

https://shop.example.com/mcp

Replace the example host with your installation. This is a protocol endpoint, not a page to open in a browser. The operator must have the MCP service deployed; enabling access does not install it.

2. Connect your client

Add a remote MCP connection using the copied endpoint and Streamable HTTP transport. Field names vary by client.

Authentication	Setup
OAuth	Choose OAuth when supported. NetSeller supports the authorization-code flow with PKCE. Follow the NetSeller authorization page, enter your API key there and complete the connection.
Direct bearer authentication	If the client supports custom headers, configure Authorization: Bearer <your-api-key>. Replace the placeholder with the actual key.

Enter credentials in connection settings or the authorization page, never in a chat message or a committed configuration file. OAuth does not grant additional NetSeller scopes or shops.

3. Verify the connection

Refresh the client’s tool list and call netseller_list_shops with no arguments. It returns shops assigned to the API client.

Example instruction to your assistant:

List the NetSeller shops available to this connection. Do not change any data.

Select the intended shop before continuing. See Tools and permissions for access requirements and Common workflows for concrete calls.

Troubleshooting

Symptom	Check
Connection fails or endpoint returns 404/502	Verify the copied HTTPS address and ask the operator to check the MCP service and routing.
Authentication fails	Check the API client’s active state and key. Reconnect after replacing a key. Restart an expired OAuth authorization flow.
Tool is missing	Check MCP activation, its tool group and the API scopes; then refresh the client’s tool list.
Shop is missing or operation is denied	Check the API client’s shop assignments and the operation’s required scopes. Supply the intended shop ID.
Connected, but product lookup fails	Orientation access alone is insufficient: enable catalog read and grant catalog:read. Select a valid language for that shop.
Write fails with a validation or conflict error	Follow the write and retry rules; reconnecting will not resolve a stale resource version.