didi-ridelisted

# DiDi Ride (滴滴出行) Drive the user's **DiDi (滴滴出行)** account through the DiDi MCP server: book rides, estimate fares, track orders, cancel, and plan routes. The `didi` BYOC connector injects one env var into the sandbox: - `DIDI_MCP_KEY` — the user's DiDi MCP key. **Secret — never echo, print, or log it.** If `DIDI_MCP_KEY` is missing, tell the user to connect the DiDi connector at [auth.acedata.cloud/user/connections](https://auth.acedata.cloud/user/connections) (they get the key by scanning the QR in the 滴滴出行 App or via <https://mcp.didichuxing.com/claw>). ## CLI The skill ships a stdlib-only helper that speaks the MCP Streamable-HTTP protocol to DiDi. **Run this resolver at the top of every Bash block below** — each Bash call is a fresh shell, and `$SKILL_DIR` points at the LAST skill loaded this turn, so anchor on our own script: ```bash DIDI="$SKILL_DIR/scripts/didi.py"; [ -f "$DIDI" ] || DIDI=$(find /tmp -maxdepth 8 -path '*/skills/*/scripts/didi.py' 2>/dev/null | head -1) [ -f "$DIDI" ] || { echo "didi-ride script not found (SKILL_DIR=$SKILL_DIR)" >&2; exit 1; } ``` Two commands: ```bash python3 $DIDI list # list tools + their JSON input schemas python3 $DIDI call <tool> '<json-args>' # call any tool ``` **Always check `references/api_references.md` for the exact tool + parameter names before calling.** When unsure, run `python3 $DIDI list` — it returns the authoritative input schema for every tool straight from DiDi. Do **not** guess