AgentHubAgentHub

meshtastic MCP Setup & Guide

MCP ServerMCP RegistryOfficial

io.github.meshtastic/meshtastic-mcp · v0.4.0

Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP.

Copy the install config on this page first, then verify docs and permissions upstream.

Overview

Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP. meshtastic-mcp is a MCP Server listed from MCP Registry. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

Use cases

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-11-21
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from official-mcp-registry
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 官方认证推荐 (A+)·Maintained by official/verified teams, audited for standard MCP protocol compliance.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window

Pre-fill Environment Variables (Optional)

Privacy Guarantee: Keys are replaced 100% locally in your browser memory and are NEVER uploaded or stored on any server.
Click to copy snippet
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Setup tutorial

  1. Open the meshtastic-mcp page and confirm this MCP Server (source: MCP Registry).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add meshtastic-mcp -- uvx meshtastic-mcp

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "meshtastic-mcp": {
      "command": "uvx",
      "args": [
        "meshtastic-mcp"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for meshtastic-mcp

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for meshtastic-mcp?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Missing required environment variable or authentication failure?

meshtastic-mcp requires environment variables (MESHTASTIC_FIRMWARE_ROOT、MESHTASTIC_MCP_TCP_HOST、MESHTASTIC_MCP_TOOLSETS、MESHTASTIC_MCP_READ_ONLY、MESHTASTIC_MCP_CONFIRM、MESHTASTIC_MCP_DATA_DIR、MESHTASTIC_UI_CAMERA_DEVICE、MESHTASTIC_UHUBCTL_LOCATION_TESTER、MESHTASTIC_PIO_BIN、MESHTASTIC_ANDROID_ROOT、MESHTASTIC_APPLE_ROOT). Ensure you have added valid keys under the 'env' object in your config file without trailing whitespace.

Fix Snippet
// .cursor/mcp.json 或 claude_desktop_config.json
{
  "env": {
    "API_KEY": "your_actual_key_here"
  }
}

Tool Mock Playground

Sandbox

meshtastic-mcp Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: meshtastic_mcpExecute the core tool interface of meshtastic-mcp
Request ArgumentsJSON Schema
{
  "target": "meshtastic-mcp",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • PR review
  • Changelog generation
  • Cross-repo issue search
When NOT to Use
  • Replacing human security audit
  • Unauthorized repo access
Recommended Workflow Pairing:View Scenario →

meshtastic-mcp + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

insurance-advisor-china

v2.4.21

SkillClawHub7410.3k

io.clawhub.mnetfairy/insurance-advisor-china

中国大陆AI保险顾问。为个人和家庭提供全方位的保险咨询、产品对比、方案设计、投保指导。当用户询问保险配置、保险方案、产品对比、重疾险/医疗险/寿险/意外险/储蓄险推荐、保费计算、保障缺口分析、需求分析、核保合规、理赔等问题时使用。发布产物仅含 SKILL.md + 3 个只读参考文件(references/products.json、insurance-knowledge.md、compliance.md)+ 3 个运行时脚本(needs_analyzer / premium_calculator / plan_designer);数据清洗脚本与回归测试脚本是本地维护工具,不随发布产物分发。

source

ai-insurance-advisor

v2.4.21

SkillClawHub8110.4k

io.clawhub.mnetfairy/ai-insurance-advisor

中国大陆保险顾问。本 skill 覆盖 8 项能力:保险需求分析(needs_analyzer.py)、产品对比(premium_calculator.py + 本地 products.json)、保费计算(premium_calculator.py)、方案设计(plan_designer.py)、保险知识问答(insurance-knowledge.md)、合规要点提示(compliance.md)、朋友圈/社交营销文案生成(agent LLM 生成,无专属脚本)、培训话术支持(agent LLM 生成,无专属脚本)。不提供核保预审、理赔代办、代理人展业工具等能力——这些场景请转人工或调用专业服务。发布产物仅含 SKILL.md + 3 个只读参考文件 + 3 个运行时脚本(needs_analyzer / premium_calculator / plan_designer);数据清洗与回归测试脚本为本地维护工具,不随发布产物分发。

source

中文公文写作

v2.0.63

SkillClawHub7412k

io.clawhub.gongyu0918-debug/chinese-official-writing

用于中文公文、事务性材料和新闻稿件的起草、改写、压缩、润色、审校、文种核对、去口语化、降 AI 味及 Word 格式处理,适用于机关、企事业单位、学校和新闻机构。涵盖申请、请示、报告、通知、通告、意见、决定、决议、议案、公报、命令、函、复函、批复、说明、方案、纪要、公告、公示、通报、制度、规定、办法、细则、操作规程、工作要点、总结、调研、讲话、致辞、主持词、述职、可研、审查材料、技术需求、新闻消息、编者按、新闻评论,以及采购、整改、反馈和 AI 算力等场景。

source

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: meshtastic-mcp
HTML
<a href="https://myagenthub.cn/p/io.github.meshtastic/meshtastic-mcp" title="Listed on AgentHub: meshtastic-mcp" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.github.meshtastic/meshtastic-mcp?lang=en" alt="Listed on AgentHub: meshtastic-mcp" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: meshtastic-mcp](https://myagenthub.cn/badge/io.github.meshtastic/meshtastic-mcp?lang=en)](https://myagenthub.cn/p/io.github.meshtastic/meshtastic-mcp)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.github.meshtastic/meshtastic-mcp",
  "type": "mcp-server",
  "version": "0.4.0",
  "displayName": "meshtastic-mcp",
  "description": "Discover, drive, observe, and test Meshtastic devices and companion apps over serial and TCP.",
  "repository": {
    "url": "https://github.com/meshtastic/meshtastic-mcp",
    "source": "github"
  },
  "distribution": {
    "packages": [
      {
        "registryType": "pypi",
        "identifier": "meshtastic-mcp",
        "version": "0.4.0",
        "transport": "stdio",
        "environmentVariables": [
          {
            "name": "MESHTASTIC_FIRMWARE_ROOT",
            "description": "Path to a Meshtastic firmware checkout. Optional — enables the firmware capability (build/flash/boards/userprefs). Core device/admin/recorder tools work without it."
          },
          {
            "name": "MESHTASTIC_MCP_TCP_HOST",
            "description": "host[:port] of a meshtasticd TCP node to surface in list_devices (default port 4403)."
          },
          {
            "name": "MESHTASTIC_MCP_TOOLSETS",
            "description": "Comma-separated tool groups to expose: core, firmware, hardware, android, discord, replay, rf, local-model. Unset or 'all' exposes every group; a hidden tool cannot be called."
          },
          {
            "name": "MESHTASTIC_MCP_READ_ONLY",
            "description": "Set to 1 to hide every tool that can change device or host state."
          },
          {
            "name": "MESHTASTIC_MCP_CONFIRM",
            "description": "Confirmation policy for destructive tools. 'agent' runs a tool called with confirm=True; 'human' asks the user through elicitation before an irreversible tool (factory_reset, erase_and_flash, nrf52_factory_erase, vanity_apply, destructive esptool/nrfutil/picotool calls) even when confirm=True is passed."
          },
          {
            "name": "MESHTASTIC_MCP_DATA_DIR",
            "description": "Directory for recorder JSONL logs and persistent data. Defaults to platformdirs user-data-dir, then cwd. Set this to keep recorder data in a known location."
          },
          {
            "name": "MESHTASTIC_UI_CAMERA_DEVICE",
            "description": "Camera device index or path for capture_screen (default: 0). Role-specific overrides: MESHTASTIC_UI_CAMERA_DEVICE_TESTER, _DUT, etc."
          },
          {
            "name": "MESHTASTIC_UHUBCTL_LOCATION_TESTER",
            "description": "uhubctl USB hub location for the TESTER role port (e.g. '1-1'). Enables uhubctl_power/uhubctl_cycle against that role. Suffix varies by role: _DUT, _RELAY, etc."
          },
          {
            "name": "MESHTASTIC_PIO_BIN",
            "description": "Path to the PlatformIO CLI binary. Searched in order: this env var, ~/.platformio/penv/bin/pio, then PATH. Only needed if PlatformIO is not on PATH."
          },
          {
            "name": "MESHTASTIC_ANDROID_ROOT",
            "description": "Path to a Meshtastic-Android source checkout (directory containing gradlew). Optional — enables building the APK from source via scripts/build_android_apk.sh. If unset, scripts default to cloning fresh or using a release APK."
          },
          {
            "name": "MESHTASTIC_APPLE_ROOT",
            "description": "Path to a Meshtastic-Apple source checkout (directory containing Meshtastic.xcworkspace). Optional — enables building the iOS Simulator .app from source via scripts/build_apple.sh. If unset, scripts clone fresh."
          }
        ]
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [],
  "provenance": {
    "origin": "official-mcp-registry",
    "originalId": "io.github.meshtastic/meshtastic-mcp",
    "originalUrl": "https://registry.modelcontextprotocol.io/v0.1/servers/io.github.meshtastic%2Fmeshtastic-mcp/versions/latest",
    "isOfficial": true,
    "status": "active"
  }
}
meshtastic MCP Setup & Guide - AgentHub