CUSTOMER STORY / SEMICONDUCTORS
How Nordic Semiconductor deploys Kapa across docs, support form and MCP server
Nordic Semiconductor
Semiconductors
“Kapa connects every source we have -
PDFs, codebase, versioned documentation -
and keeps it all in sync as we ship.”
Diedre Casey
AI Integration Manager
About Nordic Semiconductor
Nordic Semiconductor is a Norwegian fabless company headquartered in Trondheim and a long-standing leader in ultra-low-power wireless. Its portfolio spans Bluetooth LE and short-range SoCs (the nRF52, nRF53, and nRF54 Series), Wi-Fi (nRF70 Series), and cellular IoT for LTE-M and NB-IoT (the nRF91 Series and newer cellular families). Developers build on the nRF Connect SDK, which pairs the open-source Zephyr project with Nordic software, and lean heavily on the docs site and the DevZone community, where a large base of engineers asks detailed, protocol-specific questions.
That mix of deep, protocol-specific documentation and a highly active support community is what shapes the deployment below. The goal is to put a precise, source-cited answer in each place a Nordic engineer already turns, from the docs to the support queue to the tools they build with.
Challenge
Nordic's answers live across documentation, datasheets, PDFs, SDK and GitHub code, and years of DevZone support history. Bringing up a design on a specific nRF Series with the right SDK version means pulling together many sources, and the support queue carries a high share of questions the knowledge base already answers.
The task is to make that deep, fast-moving body of wireless knowledge instantly answerable, in the place each engineer is already working.
Solution
Nordic deploys Kapa across its docs, its support intake, and its own products, all on one connected corpus. Kapa ingests documentation, GitHub code, datasheets and PDFs, and YouTube content alongside S3 content and historical support tickets, and layers in Custom Answers for canonical responses.
The corpus stays current as SDKs and silicon evolve, so every surface draws on the same source of truth.
Documentation Agent
Deployed on docs.nordicsemi.com, it answers natural-language questions with precise, source-cited responses from user guides, SDK references, and datasheets. Rather than piecing together a configuration across several documents, an engineer finds the exact answer in seconds, with links back to source, and answers stay accurate as the nRF Connect SDK and hardware evolve because they are grounded in the current docs.
Play video
Support Form Agent
Sitting at the DevZone support form, it reads the drafted question and suggests a fix before submission, escalating cleanly to a human when it cannot help. This deflects the repeat questions the knowledge base already covers, which cuts queue volume and frees Nordic's support engineers for genuinely novel problems, while the tickets that do come through arrive with more context and resolve faster.
Play video
MCP Server
A hosted MCP endpoint feeds product context to coding agents like Claude Code and Cursor as developers work, grounding them in the nRF Connect SDK, APIs, and hardware specifics. For embedded and wireless development, reasoning from authoritative Nordic sources keeps generated code aligned with how the parts and protocols actually behave.
Play video
Why it works
Every deployment runs on the same corpus and answer engine, so an answer in the docs, at the support form, inside a Nordic-built experience, through the Retrieval API, or in a coding agent stays consistent and traceable to source.
Nordic adds a surface without rebuilding its knowledge base, and updates reach every agent at once as SDKs and silicon evolve, which is how a focused documentation and support organization keeps pace with a global engineering community.