"Accessing Gmail Services or Information" matching MCP servers:

An MCP server for source-grounded, page-cited evidence retrieval tailored for embedded and firmware development, returning verbatim snippets with exact citations or 'no match' to prevent fabrications.

An MCP server that enables AI assistants to control Siglent SDS oscilloscopes over a local network using SCPI commands. It allows users to measure signals, configure channel and acquisition settings, and capture waveforms or screenshots through natural language.

AI-driven USB oscilloscope control via FastMCP, enabling waveform capture, CSV export, and frequency measurements on PicoScope, Hantek, or a built-in simulator.

Enables Claude Code sessions to control a Rigol DS1054Z oscilloscope over USB, reading identity, settings, measurements, screenshots and waveforms, and applying undoable or destructive changes such as channel, timebase, trigger and acquisition configuration, run control, autoscale and reset. Tool calls come with read-only and destructive hints so safe operations can be auto-approved while risky ones stay behind user approval.

A local MCP server that connects Claude Code or any MCP-compatible AI assistant to a Robonine robot arm.

Enables LLMs to control RIGOL oscilloscopes over SCPI via LAN or USB, including configuring channels/timebase/trigger, taking measurements, capturing waveforms and screenshots, decoding serial protocols, running FFT analysis, and controlling the built-in AFG.

MCP server for controlling CNC machines via Universal GCode Sender. Lets Claude (or any MCP-compatible AI assistant) connect to a CNC machine, inspect G-code, and issue motion commands — all through the UGS Pendant REST API.

AI-powered FPGA power estimation assistant that wraps Xilinx PDM API as MCP services for natural language power modeling and analysis.

A Model Context Protocol (MCP) server for ROS 2 that enables GitHub Copilot and other AI agents to interact with ROS 2 systems. This server provides tools for monitoring, debugging, and managing ROS 2 nodes, topics, services, and TF2 frames.

Enables controlling robots in ROS environments through natural language, supporting topics, services, actions, and GUI tools.

Enables AI agents to debug embedded systems by providing a comprehensive interface for GDB operations across multiple architectures like ARM and x86. It supports remote debugging via gdbserver or QEMU, allowing for detailed inspection of memory, registers, stack frames, and variables.

Provides read-only retrieval of STM32 datasheet and reference manual content with exact citations, page numbers, register details, and source hashes so Claude can answer questions or generate code from verified evidence.

An MCP server that judges hardware behavior against timing or serial contracts, returning pass/marginal/fail verdicts for coding agents to iterate on real signal measurements.

Talk to your Flipper Zero from Claude Code — or any MCP client. Storage, app deployment, screen capture, button automation, JavaScript execution on the device, and honest answers about what is nearby.

Local or self hosted LLM server for Labgrid hardware-in-the-loop device operations

Lets MCP clients such as Codex control an ESP32 face through semantic expressions, status and capability reads, and neutral resets over a local STDIO or loopback HTTP interface.

MCP server for controlling MicroPython devices (ESP32, RP2040, etc.) via USB Serial or WebREPL, enabling code execution, file operations, and device management from MCP clients.

Enables lossless parsing, inspection, validation, simulation, and creation or editing of FATEK .ldr ladder-logic files through local stdio MCP tools, including a user-import-verified start/stop template. New files are written to an artifacts directory so existing files and original samples are never overwritten.

An MCP server for controlling KR-series relay controllers via serial, TCP, or UDP, featuring auto-discovery, relay control, and advanced PLC capabilities.

Enables reading and configuring an Unfolded Circle Remote Two or Remote 3 through the official Core REST API, exposing activities, touchscreen pages, profiles, integration entities, and physical-button mappings to MCP clients.