@dai_ming/plugin-didi-ride

OpenClaw native plugin for Didi ride capabilities. The plugin stores one shared Didi MCP Key under the OpenClaw state directory, then proxies calls to the official Didi MCP Server.

Contents

• index.js: OpenClaw native extension, registers didi-ride__* tools.
• openclaw.plugin.json: OpenClaw runtime plugin manifest.
• openclaw-plugin.json: gateway compatibility manifest.
• skills/didi-ride/SKILL.md: agent guidance for binding and using Didi tools.

Global Binding

The binding is global for the pod, not per agent.

Default state file:

$OPENCLAW_STATE_DIR/didi-ride/binding.json

In the managed pod this resolves to:

/data/didi-ride/binding.json

Calling didi-ride__bind_key again replaces the key. Agents should never echo the raw key back to the user.

DIDI_MCP_KEY can also be provided by environment variable. When present, it takes precedence over the persisted file.

Didi MCP Endpoint

Default production endpoint:

https://mcp.didichuxing.com/mcp-servers

The plugin appends ?key=<MCP_KEY> at request time and never returns the raw key in tool output.

For sandbox/debug usage, bind with a custom endpoint:

{
  "mcp_key": "YOUR_MCP_KEY",
  "endpoint": "https://mcp.didichuxing.com/mcp-servers-sandbox"
}

Install Through claw-gateway

Add the plugin to installPlugins:

installPlugins:
  - "@dai_ming/[email protected]"

For managed default installs, create or update the plugin registry record:

{
  "name": "plugin-didi-ride",
  "installPackage": "@dai_ming/plugin-didi-ride",
  "displayName": "Didi Ride",
  "category": "builtin",
  "recommendedVersion": "0.1.5",
  "enabled": true,
  "npmRegistry": "https://registry.npmjs.org"
}

Publish

cd packages/plugin-didi-ride
npm publish --registry https://registry.npmjs.org --access public