dbgprobe-mcp-server
mcpkey · packageio.github.es617/dbgprobe-mcp-server · v0.1.4
Let AI agents interact with debug probes — connect, flash, read/write memory, and reset.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
#!/usr/bin/env bash # dbgprobe (io.github.es617/dbgprobe-mcp-server), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-dbgprobe.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec uvx mcp-proxy --host 127.0.0.1 --port 8101 --pass-environment -- uvx dbgprobe-mcp-server==0.1.4 [Unit] Description=MCP server dbgprobe (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/dbgprobe WorkingDirectory=/var/lib/mcp/dbgprobe ExecStart=/opt/mcp/my-agent/bin/dbgprobe.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/dbgprobe [Install] WantedBy=multi-user.target
generated from the record, not tested yet
docker run --rm -p 127.0.0.1:8101:8000 -e DBGPROBE_BACKEND -e DBGPROBE_MCP_LOG_LEVEL -e DBGPROBE_JLINK_PATH -e DBGPROBE_JLINK_GDBSERVER_PATH -e DBGPROBE_JLINK_DEVICE -e DBGPROBE_INTERFACE -e DBGPROBE_SPEED_KHZ -e DBGPROBE_MCP_PLUGINS -e DBGPROBE_MCP_TOOL_SEPARATOR ghcr.io/astral-sh/uv:python3.12-bookworm-slim sh -c 'uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx dbgprobe-mcp-server==0.1.4'
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-17T23:55:47+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
dbgprobe:
image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
command:
- sh
- -c
- uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx dbgprobe-mcp-server==0.1.4
ports:
- 127.0.0.1:8101:8000
volumes:
- uv-cache:/root/.cache/uv
healthcheck:
test:
- CMD
- python3
- -c
- import urllib.request; urllib.request.urlopen('http://127.0.0.1:8000/status')
interval: 30s
timeout: 5s
retries: 5
start_period: 2m
restart: unless-stopped
environment:
DBGPROBE_BACKEND: ${DBGPROBE_BACKEND}
DBGPROBE_MCP_LOG_LEVEL: ${DBGPROBE_MCP_LOG_LEVEL}
DBGPROBE_JLINK_PATH: ${DBGPROBE_JLINK_PATH}
DBGPROBE_JLINK_GDBSERVER_PATH: ${DBGPROBE_JLINK_GDBSERVER_PATH}
DBGPROBE_JLINK_DEVICE: ${DBGPROBE_JLINK_DEVICE}
DBGPROBE_INTERFACE: ${DBGPROBE_INTERFACE}
DBGPROBE_SPEED_KHZ: ${DBGPROBE_SPEED_KHZ}
DBGPROBE_MCP_PLUGINS: ${DBGPROBE_MCP_PLUGINS}
DBGPROBE_MCP_TOOL_SEPARATOR: ${DBGPROBE_MCP_TOOL_SEPARATOR}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-17T23:55:47+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: dbgprobe
namespace: mcp
labels: &id001
app: dbgprobe
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: dbgprobe
image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
ports:
- containerPort: 8000
name: http
env:
- name: DBGPROBE_BACKEND
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_BACKEND
- name: DBGPROBE_MCP_LOG_LEVEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_MCP_LOG_LEVEL
- name: DBGPROBE_JLINK_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_JLINK_PATH
- name: DBGPROBE_JLINK_GDBSERVER_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_JLINK_GDBSERVER_PATH
- name: DBGPROBE_JLINK_DEVICE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_JLINK_DEVICE
- name: DBGPROBE_INTERFACE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_INTERFACE
- name: DBGPROBE_SPEED_KHZ
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_SPEED_KHZ
- name: DBGPROBE_MCP_PLUGINS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_MCP_PLUGINS
- name: DBGPROBE_MCP_TOOL_SEPARATOR
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_MCP_TOOL_SEPARATOR
command:
- sh
- -c
- uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx dbgprobe-mcp-server==0.1.4
readinessProbe:
httpGet:
path: /status
port: http
initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: dbgprobe
namespace: mcp
spec:
selector:
app: dbgprobe
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-17T23:55:47+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
dbgprobe:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: dbgprobe
image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim
ports:
- containerPort: 8000
name: http
env:
- name: DBGPROBE_BACKEND
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_BACKEND
- name: DBGPROBE_MCP_LOG_LEVEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_MCP_LOG_LEVEL
- name: DBGPROBE_JLINK_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_JLINK_PATH
- name: DBGPROBE_JLINK_GDBSERVER_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_JLINK_GDBSERVER_PATH
- name: DBGPROBE_JLINK_DEVICE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_JLINK_DEVICE
- name: DBGPROBE_INTERFACE
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_INTERFACE
- name: DBGPROBE_SPEED_KHZ
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_SPEED_KHZ
- name: DBGPROBE_MCP_PLUGINS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_MCP_PLUGINS
- name: DBGPROBE_MCP_TOOL_SEPARATOR
valueFrom:
secretKeyRef:
name: mcp-credentials
key: DBGPROBE_MCP_TOOL_SEPARATOR
command:
- sh
- -c
- uvx mcp-proxy --host 0.0.0.0 --port 8000 --pass-environment -- uvx dbgprobe-mcp-server==0.1.4
readinessProbe:
httpGet:
path: /status
port: http
initialDelaySeconds: 10
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: DBGPROBE_BACKEND, DBGPROBE_MCP_LOG_LEVEL, DBGPROBE_JLINK_PATH, DBGPROBE_JLINK_GDBSERVER_PATH, DBGPROBE_JLINK_DEVICE, DBGPROBE_INTERFACE, DBGPROBE_SPEED_KHZ, DBGPROBE_MCP_PLUGINS, DBGPROBE_MCP_TOOL_SEPARATOR. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsuvx dbgprobe-mcp-server==0.1.4 # env: DBGPROBE_BACKEND, DBGPROBE_MCP_LOG_LEVEL, DBGPROBE_JLINK_PATH, DBGPROBE_JLINK_GDBSERVER_PATH, DBGPROBE_JLINK_DEVICE, DBGPROBE_INTERFACE, DBGPROBE_SPEED_KHZ, DBGPROBE_MCP_PLUGINS, DBGPROBE_MCP_TOOL_SEPARATOR
{
"mcpServers": {
"dbgprobe": {
"command": "uvx",
"args": [
"dbgprobe-mcp-server==0.1.4"
],
"env": {
"DBGPROBE_BACKEND": "${DBGPROBE_BACKEND}",
"DBGPROBE_MCP_LOG_LEVEL": "${DBGPROBE_MCP_LOG_LEVEL}",
"DBGPROBE_JLINK_PATH": "${DBGPROBE_JLINK_PATH}",
"DBGPROBE_JLINK_GDBSERVER_PATH": "${DBGPROBE_JLINK_GDBSERVER_PATH}",
"DBGPROBE_JLINK_DEVICE": "${DBGPROBE_JLINK_DEVICE}",
"DBGPROBE_INTERFACE": "${DBGPROBE_INTERFACE}",
"DBGPROBE_SPEED_KHZ": "${DBGPROBE_SPEED_KHZ}",
"DBGPROBE_MCP_PLUGINS": "${DBGPROBE_MCP_PLUGINS}",
"DBGPROBE_MCP_TOOL_SEPARATOR": "${DBGPROBE_MCP_TOOL_SEPARATOR}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add dbgprobe -e "DBGPROBE_BACKEND=${DBGPROBE_BACKEND}" -e "DBGPROBE_MCP_LOG_LEVEL=${DBGPROBE_MCP_LOG_LEVEL}" -e "DBGPROBE_JLINK_PATH=${DBGPROBE_JLINK_PATH}" -e "DBGPROBE_JLINK_GDBSERVER_PATH=${DBGPROBE_JLINK_GDBSERVER_PATH}" -e "DBGPROBE_JLINK_DEVICE=${DBGPROBE_JLINK_DEVICE}" -e "DBGPROBE_INTERFACE=${DBGPROBE_INTERFACE}" -e "DBGPROBE_SPEED_KHZ=${DBGPROBE_SPEED_KHZ}" -e "DBGPROBE_MCP_PLUGINS=${DBGPROBE_MCP_PLUGINS}" -e "DBGPROBE_MCP_TOOL_SEPARATOR=${DBGPROBE_MCP_TOOL_SEPARATOR}" -- uvx dbgprobe-mcp-server==0.1.4
{
"mcpServers": {
"dbgprobe": {
"command": "uvx",
"args": [
"dbgprobe-mcp-server==0.1.4"
],
"env": {
"DBGPROBE_BACKEND": "${DBGPROBE_BACKEND}",
"DBGPROBE_MCP_LOG_LEVEL": "${DBGPROBE_MCP_LOG_LEVEL}",
"DBGPROBE_JLINK_PATH": "${DBGPROBE_JLINK_PATH}",
"DBGPROBE_JLINK_GDBSERVER_PATH": "${DBGPROBE_JLINK_GDBSERVER_PATH}",
"DBGPROBE_JLINK_DEVICE": "${DBGPROBE_JLINK_DEVICE}",
"DBGPROBE_INTERFACE": "${DBGPROBE_INTERFACE}",
"DBGPROBE_SPEED_KHZ": "${DBGPROBE_SPEED_KHZ}",
"DBGPROBE_MCP_PLUGINS": "${DBGPROBE_MCP_PLUGINS}",
"DBGPROBE_MCP_TOOL_SEPARATOR": "${DBGPROBE_MCP_TOOL_SEPARATOR}"
}
}
}
}
{
"servers": {
"dbgprobe": {
"type": "stdio",
"command": "uvx",
"args": [
"dbgprobe-mcp-server==0.1.4"
],
"env": {
"DBGPROBE_BACKEND": "${DBGPROBE_BACKEND}",
"DBGPROBE_MCP_LOG_LEVEL": "${DBGPROBE_MCP_LOG_LEVEL}",
"DBGPROBE_JLINK_PATH": "${DBGPROBE_JLINK_PATH}",
"DBGPROBE_JLINK_GDBSERVER_PATH": "${DBGPROBE_JLINK_GDBSERVER_PATH}",
"DBGPROBE_JLINK_DEVICE": "${DBGPROBE_JLINK_DEVICE}",
"DBGPROBE_INTERFACE": "${DBGPROBE_INTERFACE}",
"DBGPROBE_SPEED_KHZ": "${DBGPROBE_SPEED_KHZ}",
"DBGPROBE_MCP_PLUGINS": "${DBGPROBE_MCP_PLUGINS}",
"DBGPROBE_MCP_TOOL_SEPARATOR": "${DBGPROBE_MCP_TOOL_SEPARATOR}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.es617/dbgprobe-mcp-server
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.