nrf-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NRF_SDK_REF | No | SDK version to target — any git ref (tag, branch, commit SHA). Default is defined in package.json. | |
| GITHUB_TOKEN | No | GitHub API token; set explicitly to bypass the gh CLI requirement. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nrf_listA | List the contents of a directory in the nRF Connect SDK repo (nrfconnect/sdk-nrf @ main). Useful starting paths:
Returns dirs first, then files, with full paths you can pass to nrf_read. |
| nrf_readA | Read the contents of a file from the nRF Connect SDK repo (nrfconnect/sdk-nrf @ main). Works for any text file: .rst documentation, .c/.h source, CMakeLists.txt, Kconfig, prj.conf, .yaml, README.rst, etc. Use nrf_list to discover paths first. Examples:
|
| nrf_searchA | Search for code or documentation across the nRF Connect SDK repo using GitHub code search. Supports GitHub search qualifiers to narrow results:
Returns matching file paths (up to 20). Use nrf_read to fetch the content. Note: Requires GITHUB_TOKEN for reliable results (unauthenticated search is heavily rate-limited). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: nrf_list for directory listing, nrf_read for file reading, and nrf_search for content searching. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent 'nrf_' prefix with descriptive verbs (list, read, search), using snake_case uniformly. This predictable pattern enhances readability and reduces confusion.
Three tools are appropriate for the server's purpose of exploring the nRF Connect SDK repo, covering listing, reading, and searching. It's slightly minimal but reasonable for this focused domain, with no unnecessary tools.
The tool set provides complete coverage for exploring the SDK repo: listing directories, reading files, and searching content. There are no obvious gaps, as these tools enable agents to navigate and retrieve information effectively without dead ends.