Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Run, build, and validate firmware on virtual hardware from your AI agent. Hardware knowledge corpus.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://chiplab.veecle.ai/mcpRun this in your terminal
claude mcp add --transport http chiplab https://chiplab.veecle.ai/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chiplab": {
"url": "https://chiplab.veecle.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"chiplab": {
"type": "http",
"url": "https://chiplab.veecle.ai/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://chiplab.veecle.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain veecle.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Simulate & validate firmware on virtual instances of real chips, straight from your AI coding agent — no hardware.
Chiplab is a hosted MCP service. Your AI coding agent connects to it, uploads compiled firmware, runs it on a virtual instance of a real microcontroller, and reads back the UART output. You don't drive the toolchain — your agent does.
We're building the next way to develop chips, in the open and early. Today it runs Hello world! on STM32 and Nordic boards; a lot more is on the way — see [veecle.ai](https://veecle.ai). Try it, poke at it, and tell us what you'd like to see.
git clone https://github.com/veecle/chiplab && cd chiplab, then tell your agent:*"Set up Chiplab and run the stm32f4-discovery example on it."*
Your agent reads AGENTS.md, installs what it needs, builds the firmware, uploads it, runs it on the virtual board, and reports Hello world! back from the chip's UART. That's the whole loop.
Chiplab is an HTTP MCP server at https://chiplab.veecle.ai/mcp. Most clients take the standard mcpServers schema:
{
"mcpServers": { "chiplab": { "type": "http", "url": "https://chiplab.veecle.ai/mcp" } } }
On first use your client opens a browser to sign in. To verify, ask your agent to call Chiplab's discovery/help tool with no arguments.
Claude Code
If you cloned this repo, the server is already configured via .mcp.json — Claude Code will prompt you to trust it. Otherwise:
claude mcp add --transport http chiplab https://chiplab.veecle.ai/mcp
Claude Desktop / Cursor
Use the mcpServers block above in claude_desktop_config.json or .cursor/mcp.json.
VS Code
Same block in .vscode/mcp.json, but under a servers key instead of mcpServers.
Codex
TOML in ~/.codex/config.toml:
[mcp_servers.chiplab]
url = "https://chiplab.veecle.ai/mcp"
Then sign in with codex mcp login chiplab.
The contract is framework-agnostic: your agent builds an ELF → uploads it → runs it on the target board → reads the captured UART output. Runs return synchronously and are bounded to a fixed amount of virtual time.
This repo ships a ready-to-run example for every supported board, grouped by framework — bare-metal (Rust, vendor HAL), embassy-rust ([Embassy] async), zephyr-os ([Zephyr RTOS], C), freertos ([FreeRTOS], C), and threadx ([Eclipse ThreadX], C). The full board × framework matrix is in [supported-boards.md](supported-boards.md).
Toolchain and build details live in each framework's directory (examples/ /README.md for humans, AGENTS.md for agents) — your agent finds them on its own. Prefer building by hand? Each framework README has the exact commands.
To run your own firmware, build an ELF for a supported board and ask your agent to upload and run it the same way.
Adding a board example is the easiest way in: mirror an existing example for the same framework and add a row to supported-boards.md. All conventions live in [AGENTS.md](AGENTS.md) and each framework's AGENTS.md. New chip, OS, or peripheral support is server-side — open a request instead of adding an example for an unsupported board.
This is Chiplab's public home — bugs, feature ideas, and chip/OS/peripheral requests all belong in this repo's issues. Requests really do shape the roadmap — see veecle.ai/roadmap for what's planned, or come say hi on Discord.
MIT © 2026 Veecle GmbH.