atel-mcp-openclaw
v0.6.52
Published
OpenClaw plugin: bridge OpenClaw runtime to ATEL Remote MCP via DID-Sig auth
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
After publishing to npm:
npx -y atel-mcp-openclaw --identity /path/to/.atel/identity.jsonFrom this repository:
ATEL_IDENTITY_PATH=/path/to/.atel/identity.json ./scripts/install-openclaw-plugin.shDefaults:
serverBaseUrl=https://atelai.xyzplatformBaseUrl=https://api.atelai.xyz
The installer copies the plugin into ~/.openclaw/extensions/atel-mcp, installs
runtime dependencies, writes plugins.entries.atel-mcp.config, validates
OpenClaw config, and attempts to restart openclaw-gateway.service.
Verify
openclaw plugins inspect atel-mcp --jsonExpected:
status=loaded
toolNames=["atel_mcp"]Then ask the Telegram bot:
Use ATEL MCP to call atel_whoami and tell me the current DID, environment, and 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.
