6b15571e14
* Start of MCP server and test suite * Add MCP server for interacting with meshtastic devices and testing framework / TUI * Update mcp-server/README.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * fix mcp-server review feedback from thread Agent-Logs-Url: https://github.com/meshtastic/firmware/sessions/91dc128a-ed50-4d07-8bb2-3dc6623a05f7 Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com> * Enhance StreamAPI and PhoneAPI for improved log record handling and concurrency control * Semgrep fixes * Trunk and semgrep fixes * optimize pio streaming tee file writes Agent-Logs-Url: https://github.com/meshtastic/firmware/sessions/04e26c6b-6a2b-45be-bbeb-79ae4d0be633 Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com> * chore: remove redundant log handle assignment Agent-Logs-Url: https://github.com/meshtastic/firmware/sessions/04e26c6b-6a2b-45be-bbeb-79ae4d0be633 Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com> * Consolidate type imports and remove placeholder test files * Add tests for config persistence and more exchange messages * Refactor position test to validate on-demand request/reply behavior * Remove position request/reply test and update README for telemetry behavior * Fix transmit history file to get removed on factory reset --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
2.8 KiB
2.8 KiB
Claude Code slash commands for the mcp-server test suite
Three AI-assisted workflows wrapping mcp-server/run-tests.sh and the meshtastic MCP tools. Each one has a twin in .github/prompts/ for Copilot users.
| Slash command | What it does | Copilot equivalent |
|---|---|---|
/test [args] |
Runs the test suite (auto-detects hardware) and interprets failures | .github/prompts/mcp-test.prompt.md |
/diagnose [role] |
Read-only device health report via the meshtastic MCP tools | .github/prompts/mcp-diagnose.prompt.md |
/repro <test> [n=5] |
Re-runs one test N times, diffs firmware logs between passes and failures | .github/prompts/mcp-repro.prompt.md |
Why two surfaces
The Claude Code commands and Copilot prompts cover the same three workflows but each speaks its host's idiom:
- Claude Code (
/test) uses$ARGUMENTSfor pass-through, has direct access to Bash + all MCP tools registered in the user's settings, and runs in the terminal context. - Copilot (
/mcp-test) runs in VS Code's agent mode; it has terminal + MCP access too but typically asks the operator to confirm inputs interactively.
A contributor using either IDE gets equivalent assistance. Keep the two in sync when behavior changes — the diff of intent should be minimal.
House rules
- No destructive writes without explicit operator approval. Skills that could reflash, factory-reset, or reboot a device must describe the action and stop — the operator authorizes.
- Interpret failures, don't just echo them. The skill body should pull firmware log lines from
mcp-server/tests/report.html(theMeshtastic debugsection, attached bytests/conftest.py::pytest_runtest_makereport) and classify the failure. - Keep MCP tool calls sequential per port. SerialInterface holds an exclusive port lock; two parallel tool calls on the same port deadlock.
- Never speculate about root cause. If the evidence doesn't support a classification, say "unknown" and list what you'd need to disambiguate.
Adding a new command
-
Write the Claude Code version at
.claude/commands/<name>.mdwith YAML frontmatter:--- description: one-line purpose (used for auto-invocation by the model) argument-hint: [optional-hint] --- -
Write the Copilot equivalent at
.github/prompts/mcp-<name>.prompt.mdwith:--- mode: agent description: ... --- -
Add the row to the table above. Cross-link in both bodies.
-
Smoke-test on Claude Code first (
/<name>should appear in autocomplete), then in VS Code Copilot (/mcp-<name>in Chat).