This document defines the product and engineering specification for a Model Context Protocol (MCP) server built around the EveApps-BT82X repository.
The goal is to turn the BT820 SDK and sample repository into an AI-assisted developer workflow that helps users:
- find the right sample faster
- understand BT820 / EVE API symbols
- map user requirements to commands and samples
- generate minimal screen scaffolds
- validate common mistakes in BT820 application code (TBD)
- generate valid build commands for supported target configurations
This MCP server is intended to support both learning and production development workflows.
Recommended positioning names:
- BT820 Application Builder Assistant
- BT820 Sample Navigator
- BT820 API Copilot
- BT820 Board Porting Assistant (TBD)
Primary value proposition:
- reduce onboarding time for new developers
- reduce repeated support / FAE effort
- improve discoverability of samples and APIs
- provide repo-grounded guidance instead of generic code generation
The MCP server should:
- index commands, constants, registers, and samples from the repo
- expose repo-grounded resources to AI clients
- provide tools for search, explanation, build guidance, and scaffold generation
- produce deterministic, structured outputs
- prioritize existing repo samples over invented code patterns
The MCP server should not:
- modify the repo automatically
- generate full production applications from scratch
- replace the BT820 programming guide or datasheet
- invent symbols, macros, or APIs not present in indexed source data
- require a vector database in the first release
Typical needs:
- Which sample should I start from?
- What does this command do?
- How do I build for RP2040?
Typical needs:
- How do I build a touch menu?
- Which commands are involved in animation?
- Can you generate a minimal screen skeleton?
Typical needs:
- Which repo sample best matches this customer use case?
- What does
REG_TOUCH_TAGmean? - Why does this code look structurally wrong?
The system consists of two major parts:
- offline indexer
- MCP server
The indexer scans the EveApps-BT82X repo and generates structured JSON artifacts:
commands.jsonsamples.jsonregisters.jsonbuild_matrix.jsonfeature_graph.json
The MCP server loads these JSON artifacts and exposes:
- resources
- tools
- prompts
Recommended implementation:
- Language: TypeScript
- Runtime: Node.js 20+
- Transport: stdio
- Data source: local JSON files
This guide explains how to connect the BT820 MCP Server to your local EveApps-BT82X workspace, enabling AI assistants to understand the BT820 SDK, browse samples, and provide project-aware assistance.
Before you begin, make sure you have:
- Node.js (version 18 or later recommended)
You can verify your Node.js installation:
node -v
npm -vClone or download the EveApps-BT82X repository to your local machine.
Example:
git clone https://github.com/Bridgetek/EveApps-BT82XSuppose the repository is located at:
D:\EveApps-BT82Xnpm install -g bt820-mcp-serverAfter installation, you can verify it by running:
bt820-mcp-server --helpOpen the EveApps-BT82X folder in Visual Studio Code.
Open the EveApps-BT82X folder in Visual Studio Code.
In the root directory of the repository, create a new file named:
.mcp.json
Add the following content:
{
"mcpServers": {
"bt820": {
"command": "bt820-mcp-server",
"args": [
"--eveapps",
"D:\\EveApps-BT82X"
]
}
}
}
Replace:
D:\\EveApps-BT82X
with the actual path to your local EveApps-BT82X repository.
For example:
{
"mcpServers": {
"bt820": {
"command": "bt820-mcp-server",
"args": [
"--eveapps",
"C:\\Users\\John\\Documents\\EveApps-BT82X"
]
}
}
}
Note
- Use double backslashes (\) in Windows paths inside JSON files.
- Alternatively, you may use forward slashes: "D:/EveApps-BT82X"
Save the .mcp.json file.
Close and reopen Visual Studio Code (or reload the window) so that the MCP configuration is detected and the BT820 MCP Server starts.
Open Claude Code and run:
/mcp
Confirm that the BT820 MCP Server appears in the list and shows a connected status.
Once connected, you can start using the server by asking questions such as:
What tools do you have for BT820?
If the MCP server is configured correctly, Claude Code should list the available BT820 development tools.
Open the Claude Desktop MCP configuration file("claude_desktop_config.json") and add a new BT820 server entry.
Example configuration:
{
"mcpServers": {
"bt820": {
"command": "bt820-mcp-server",
"args": [
"--eveapps",
"D:\\EveApps-BT82X"
]
}
}
}
Replace the path with the location of your local EveApps-BT82X repository.
Save the configuration file, completely close Claude Desktop, and then launch it again to ensure the new MCP configuration is loaded.
Start a new conversation and ask:
What tools do you have for BT820?
If the server starts successfully, Claude Desktop will be able to access the BT820-specific tools provided by the MCP server.
Verify that the package was installed successfully:
npm install -g bt820-mcp-serverThen check:
bt820-mcp-server --helpIf the command is still not found, ensure that your global npm installation path is included in your system PATH environment variable.
Check that:
- .mcp.json is located in the root of the EveApps-BT82X workspace.
- The --eveapps path points to the correct local repository.
- Visual Studio Code has been restarted after creating or modifying .mcp.json.
EveApps-BT82X/
│
├── .mcp.json
├── common/
├── SampleApp/
└── ...