Learn from example requests

Study these requests to see how to describe goals, constraints, and verification steps to Nordic MCP. This page includes the following examples:

• Create a Bluetooth LE temperature application: Scaffolds an nRF54L15 DK application, then adds Bluetooth LE temperature reporting and smartphone LED control.
• Set up and test the Hello World sample: Prepares the SDK environment, then builds, programs, and verifies the UART output of the sample.
• Demonstrate Bluetooth LE shorter connection intervals: Builds a demo from the shorter_conn_intervals sample, then reports the negotiated intervals and latency.
• Integrate an OLED display and a GNSS receiver: Adds two I2C devices and displays the time, date, location, and satellite count.
• Optimize the power consumption of a Bluetooth LE application: Measures current with PPK2 before and after each optimization, while keeping UART enabled.
• Diagnose a repeatable crash: Correlates UART logs with GDB evidence to find the root cause without changing the code.
• Investigate an I2C read error: Uses trusted Nordic sources to find why sensor register reads return -EIO.

Every example follows these practices:

• Each request asks for one concrete outcome.
• Setup and Development are separate phases. Setup ends with a verification build, and Development continues in a fresh chat.

When you write your own request, replace the paths, versions, targets, and requirements with values from your project. For more information about the phases, see Use guided workflows.