using-nordic-mcp

Using Nordic MCP

Nordic MCP is a hosted HTTP MCP server (https://aidev.nordicsemi.com/mcp, OAuth via myNordic) that gives AI assistants access to nRF Connect SDK (NCS) documentation, setup, build, program, and debug workflows. This skill encodes Nordic's official guidance for prompting it well.

Mentioning "Use Nordic MCP" is enough — the server exposes its own tools, prompts, and resources and routes the request. Do not micro-manage individual tool names unless you need a specific fact or resource.

1. Define context first

Before acting, establish (ask the user if missing):

• NCS version and its location on disk.
• Full board target (Zephyr board target, e.g. nrf5340dk/nrf5340/cpuapp) or DK name.
• Project type: freestanding app, NCS workspace, module, sample, or existing project.
• Project path, plus any commands, logs, error messages, or config snippets.

If the board target is unknown, resolve it with Nordic sources before relying on it for build or programming.

2. Ask for Nordic sources

Use nordicsemi_search_sources with full-sentence questions for facts that change between SDK versions: board targets, Kconfig symbols, devicetree bindings, nrfutil syntax, recommended tools / J-Link versions. Read these resources when relevant:

• nrfutil-manual — verify exact nrfutil syntax before suggesting commands.
• embedded-code-guidance-ncs-zephyr — read before reviewing or writing Zephyr code.

Prefer Nordic sources over general model knowledge for Zephyr APIs, Kconfig, and devicetree details.

3. Action guardrails

PAUSE and ask for explicit confirmation before any action that affects hardware or project files:

• Programming, erasing, or recovering a device.
• Changing the NCS version.
• Modifying project files during a migration.
• Selecting among multiple connected boards — confirm which device first.

4. Separate chats for setup vs. development

• Setup phase: installing NCS/toolchain, preparing the environment, scaffolding a starter project, running a verification build.
• Development phase: building, configuring, programming, debugging, testing, monitoring UART, changing application code.

Keep these in separate chats so context stays focused. Start a fresh chat if answers drift or unrelated tasks pile up.

Common mistakes -> use instead

Avoid	Use instead
Vague task requests	Give NCS version, full board target/DK, project path, intended result
One chat mixing setup + development	Separate chats per phase
Flashing before checking connected devices	Identify the target device and confirm first
Writing Zephyr from general model knowledge	Verify APIs/Kconfig/devicetree via Nordic sources

Slash commands in this plugin

/nordic-setup-ncs, /nordic-build-debug, /nordic-search-docs, /nordic-migrate.