Claude
- Open Rake MCP in the Claude directory ↗
- Click Connect
- Sign in to your account

An AI assistant writes register names, bit positions and timing values from memory, and on hardware a value that is nearly right does not work.
Rake MCP lets your AI look them up, and work the way a firmware engineer does.
Look up the registers, bit fields and interrupts of a part in the vendor's own files, and the pins of an STM32. 935 devices: STM32, nRF51 to nRF91, ESP32, RP2040 and RP2350, AVR, Microchip SAM, TI MSPM0, and NXP i.MX RT, LPC, MCX and Kinetis. Zephyr Kconfig symbols and devicetree bindings by release.
Decode a Cortex-M HardFault from its fault registers, an ESP-IDF panic, a Zephyr fatal error, a RISC-V trap, or a register dump from a debugger.
Calculate CAN bit timing, UART baud rate, timer, I2C and watchdog values from your clock, with the register value to write and the measurement that proves it on the board.
Check the register and interrupt handler names in your code against the part, a prj.conf against a Zephyr release, a FreeRTOSConfig.h, compiler and linker flags, and ESP-IDF calls against a release.
Get a firmware engineer's working practice: what to measure first when a board hangs, resets or stays silent, the order of a bring-up, a driver or a firmware update, the faults to test against, and coding rules for C, C++ and Rust.
Every tool only reads. Every lookup names its source and its licence, and the server says so when it has no data for a part. No datasheet text is included.
Free with a Rake account: a code by email, or one click with GitHub or Google. No password and no card. The same account opens Rake, which builds, flashes and debugs firmware on your board.
Go through the faults the field produces and find what the code does under each.
https://mcp.rakelabs.ai/mcphttps://mcp.rakelabs.ai/mcpmcp.rakelabs.aibreakGo through the faults the field produces and find what the code does under each.bring-upFirst power-on of a new board, one proven step at a time.diagnoseFind the cause of a problem seen on real hardware by tests, before any code changes.reviewA review of firmware code that ends in Block or Approve.The AI reads these server instructions before using this connector, every time.
For microcontroller firmware. The tools give exact registers, bit fields, interrupts and pins from the vendors' own files and Kconfig symbols and devicetree bindings from the Zephyr releases, compute CAN, UART, I2C, timer and watchdog values, check code and configuration against a part or a release, and decode crashes: Cortex-M fault registers, a RISC-V trap, an ESP-IDF panic, a Zephyr fatal error. Use the lookup, calc, check and decode tools instead of recalling these values from memory, also when a value seems familiar, and say so when a tool has no data for a part. Register data covers STM32, nRF51, nRF52, nRF53, nRF54L and nRF91, RP2040 and RP2350, ESP32, AVR (ATmega, ATtiny, AVR Dx and Ex), Microchip SAM C21, D, E5x and L21, TI MSPM0, and NXP i.MX RT, LPC, MCX, K32 L and Kinetis parts. says whether a part is covered. No datasheet text is included.
Before you write code for a microcontroller family, an RTOS, an SDK or a bus that has not come up in this session, call . For a symptom seen on hardware, call before you change code. To observe what the firmware does, or for a compiler, linker or macro technique, call . Before a board bring-up, a driver, an interrupt handler, a watchdog, a firmware update or low-power work, call and take its steps in order. To harden firmware, call and find what the code does under each fault. Before you call firmware done, review it with and report by rule id.
You work on firmware with an engineer who has the board. You cannot see it. The engineer is your eyes, and every claim about the hardware needs evidence from the target.
Observe before you edit. A symptom on hardware gets a measurement before it gets a code change. Most symptoms start outside the code: power, clock, reset, pins, configuration.
Ask for one observation at a time. Say where to look, the value you expect, and what each answer will mean. One clear question gets a measurement. Five get a guess.
Take the cheapest test that splits the suspects. A read beats a scope, and a scope beats a rewrite. Count what the test itself disturbs: a debugger and a print change the timing, and reading some registers clears them.
check_build_flagscheck_esp_idf_apicheck_freertos_configcheck_interrupt_handlerscheck_registerscheck_zephyr_conffind_devicefind_pinsget_bench_moveget_break_listget_firmware_rulesget_playbookget_trapslist_interruptslookup_registerlookup_zephyr_bindinglookup_zephyr_kconfigcalc_can_bit_timingcalc_i2c_timingcalc_timer_prescalercalc_uart_baudcalc_watchdog_timeoutdecode_cortex_m_faultdecode_esp_panicdecode_registersdecode_riscv_trapdecode_zephyr_fataldiagnose_symptomNone in the store listings or on the server
An AI assistant writes register names, bit positions and timing values from memory, and on hardware a value that is nearly right does not work. Rake MCP lets your AI look them up, and work the way a firmware engineer does. Look up the registers, bit fields and interrupts of a part in the vendor's own files, and the pins of an STM32.
Open its listing in the app's connector directory and connect. Sign in to your account in the browser window that opens. It uses OAuth, so the AI never sees your password. Step-by-step setup for each app is on this page.
The Rake MCP URL is https://mcp.rakelabs.ai/mcp. Paste it as a custom connector in Claude, ChatGPT, Gemini or Grok, or add it to Claude Code, Cursor or any MCP client. Setup steps.
Yes. Rake MCP is published or run by Rake Labs, so it is the official MCP server. See other official connectors.
It is listed in 1 store: Claude. Apps where it is not listed can usually still add it as a custom connector.
It has 28 tools: 17 read data and 11 change data. See every tool and its inputs.
It can change data but not delete it. 11 tools can create or update things, for example:
None that we found. None in the store listings or on the server.
Here are examples from its store listing. Type one into your AI after you connect.
No. Its answers come back as text in the chat. Connectors with interactive UI.
This page updates every day. To ask about Rake MCP from Claude, ChatGPT or a coding agent, connect the Agent Ready MCP server: it tracks ranks, tools and new listings across the AI plugin stores.