@dai_ming/plugin-didi-ride

OpenClaw native plugin for Didi ride capabilities. The plugin stores one Didi MCP Key per workspace when workspace context is available, 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.

Workspace Binding

In shared-pod runtimes, the binding belongs to the current workspace, not the physical pod.

Default workspace state file:

<workspaceDir>/.openclaw/didi-ride/binding.json

If workspace context is missing, the plugin does not read or write a pod-level fallback binding.

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.8",
  "enabled": true,
  "npmRegistry": "https://registry.npmjs.org"
}

Publish

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