Connecting to Norce via Cursor

This guide covers connecting the Norce Backend MCP Servers to Cursor. The setup is straightforward — Cursor has built-in MCP support and connects to the Norce servers directly over HTTP, with no additional tooling required.

Prerequisites

• Cursor installed (cursor.com)
• A Norce OAuth2 client with ClientId, ClientSecret, and AccountId — see Security and access
• Your Norce application ID for the environment you are working with

Step 1 — Choose global or project config

Cursor supports MCP configuration at two levels:

Use project-level config when the Norce environment is specific to one codebase — for example, a client integration project. Use global config if you regularly connect to the same Norce environment across multiple projects.

Create the file at the location you choose. If the .cursor directory does not exist, create it.

Step 2 — Add the server configuration

The config format is identical whether you are using global or project-level config. Add the servers you need and replace the placeholder values with your credentials, customer slug, and environment — YOUR-ENVIRONMENT is the environment part of the hostname, for example playground, the same as in that environment's other Norce API URLs.

{
  "mcpServers": {
    "norce-config": {
      "type": "http",
      "url": "https://YOUR-CUSTOMER-SLUG.api-se.YOUR-ENVIRONMENT.norce.tech/mcp/config/v1",
      "headers": {
        "ClientId": "your-client-id-here",
        "ClientSecret": "your-client-secret-here",
        "AccountId": "your-account-id-here"
      }
    },
    "norce-product": {
      "type": "http",
      "url": "https://YOUR-CUSTOMER-SLUG.api-se.YOUR-ENVIRONMENT.norce.tech/mcp/product/v1",
      "headers": {
        "ClientId": "your-client-id-here",
        "ClientSecret": "your-client-secret-here",
        "AccountId": "your-account-id-here"
      }
    },
    "norce-pricing": {
      "type": "http",
      "url": "https://YOUR-CUSTOMER-SLUG.api-se.YOUR-ENVIRONMENT.norce.tech/mcp/pricing/v1",
      "headers": {
        "ClientId": "your-client-id-here",
        "ClientSecret": "your-client-secret-here",
        "AccountId": "your-account-id-here"
      }
    },
    "norce-inventory": {
      "type": "http",
      "url": "https://YOUR-CUSTOMER-SLUG.api-se.YOUR-ENVIRONMENT.norce.tech/mcp/inventory/v1",
      "headers": {
        "ClientId": "your-client-id-here",
        "ClientSecret": "your-client-secret-here",
        "AccountId": "your-account-id-here"
      }
    },
    "norce-supplier": {
      "type": "http",
      "url": "https://YOUR-CUSTOMER-SLUG.api-se.YOUR-ENVIRONMENT.norce.tech/mcp/supplier/v1",
      "headers": {
        "ClientId": "your-client-id-here",
        "ClientSecret": "your-client-secret-here",
        "AccountId": "your-account-id-here"
      }
    }
  }
}

The five available server paths are: config/v1, product/v1, pricing/v1, inventory/v1, supplier/v1. Add or remove entries based on what you need.

Project config and version control: If you use project-level config, add .cursor/mcp.json to your .gitignore to avoid committing credentials.

Step 3 — Restart Cursor and verify

Cursor reads the MCP config at startup. If Cursor is already open, close and reopen it to pick up the new configuration.

After restarting, open the Cursor chat panel and check the MCP tools available. Your Norce tools should appear listed under their server names. You can also ask directly:

"Which Norce MCP tools do you have access to?"

If tools are missing, verify that the JSON is valid, credentials are correct, and the customer slug and environment in the URLs are right. See Troubleshooting and FAQ for common problems.

Step 4 — Add your instructions

Add a .cursorrules file (or use Cursor's system prompt settings) to give the AI context about your Norce environment:

You have access to the Norce Backend MCP Servers for [client name].

Application IDs:
- [Storefront name] (stage): [application ID]
- [Storefront name] (production): [application ID]

Use stage by default. Never write to production without explicit confirmation.
When tasks span multiple domains, coordinate the servers automatically.

You may also want to connect the Norce Assistant MCP alongside the Backend servers — it knows the full Norce API reference and is useful for understanding unfamiliar fields or constructing OData filters. See Working across MCP servers for how to combine it with the Backend servers and what to add to your instructions.

For a full starting-point instruction block covering all five servers, see Suggested LLM instructions.

You are ready

Try a first prompt:

"Give me a full overview of this Norce environment — applications, active price lists, and warehouse codes."

For a full list of developer workflows, see Norce Backend MCP Servers for Developers and Solution Architects.