atel-mcp-openclaw
v0.1.12
Published
OpenClaw plugin that exposes ATEL Remote MCP tools through a single bridge tool
Readme
ATEL MCP OpenClaw Plugin
This plugin registers one OpenClaw tool, atel_mcp, that bridges OpenClaw to
the ATEL Remote MCP server.
One-command Install
Recommended entry:
npx -y atel-mcp-openclawFallback if you prefer a global install:
npm install -g atel-mcp-openclaw
atel-mcp-openclawWhy npx is the default recommendation:
- it starts the guided setup immediately in one command
- it avoids relying on npm postinstall output, which some npm versions hide on successful global installs
- it keeps the user path shorter and more predictable
From this repository:
./scripts/install-openclaw-plugin.shDefaults:
serverBaseUrl=https://atelai.xyzplatformBaseUrl=https://api.atelai.xyz
Default installer behavior is guided and low-intrusion:
- copies the plugin into
~/.openclaw/extensions/atel-mcp - writes
plugins.allow,plugins.entries.atel-mcp,plugins.installs.atel-mcp - confirms the ATEL identity, Telegram callback preference, and resident-runtime help
- does not modify
tools.profile,gateway.*, ortools.elevated.*unless you explicitly pass--align-openclaw
If you really want the installer to align OpenClaw runtime knobs too:
npx -y atel-mcp-openclaw --align-openclawVerify
openclaw plugins inspect atel-mcp --jsonExpected:
status=loaded
toolNames=["atel_mcp"]Then ask the Telegram bot:
使用 ATEL MCP 调用 atel_whoami,告诉我当前 DID、environment 和 scopes。Supported actions
list: list remote ATEL MCP toolscall: call a remote ATEL MCP tool with JSON arguments
Without this OpenClaw-side installation and DID binding, Telegram messages can only use native OpenClaw or raw ATEL CLI paths; they cannot call ATEL MCP tools.
