If you have been using OpenClaw and want to extend it beyond what skills and MCP can do, plugins are the most powerful option. Here is how they work.

The short answer

An OpenClaw plugin is a TypeScript code module that runs inside the OpenClaw Gateway process. Plugins can add entirely new capabilities to the platform: messaging channels, custom tools, CLI commands, background services, authentication flows, and more. They are the most powerful and most complex extension mechanism in OpenClaw.

How plugins differ from skills and MCP

OpenClaw has three extension mechanisms, each operating at a different layer:

  • Skills are instruction files that teach the agent how to do tasks. Text only. Cross-platform. Zero infrastructure.
  • MCP connects the agent to external services through a standard protocol. Server processes that expose tools and data.
  • Plugins extend the OpenClaw platform itself with code. They run in-process with the Gateway and can change how OpenClaw works at a fundamental level.

The analogy: skills are the operating manual, MCP is the set of connectors, and plugins are new hardware modules you install into the machine.

What plugins can do

The scope of plugin capabilities is broad:

  • Messaging channels: Full inbound/outbound adapters. Matrix, Zalo, and MS Teams are all implemented as plugins.
  • Agent tools: Custom tools that appear in the tool registry and can be called by agents.
  • CLI commands: New commands or sub-commands for the OpenClaw CLI.
  • Background services: Long-running processes with start/stop lifecycle management.
  • Authentication flows: OAuth, API keys, device codes for connecting to external services.
  • Hooks: Event-driven automation triggered by OpenClaw events.
  • Skills: Plugins can bundle their own skill packages.

Installing plugins

Plugins can be installed from npm, local directories, or tarballs:

openclaw plugins install @openclaw/voice
openclaw plugins install ./my-custom-plugin
openclaw plugins list
openclaw plugins doctor

Security

Because plugins run in the same process as the OpenClaw Gateway, they have significant access to the runtime. OpenClaw mitigates risk with protections like path-traversal blocking, ownership validation, and dependency sandboxing. But plugins should be treated as trusted code. Audit before you install, and use plugins.allow allowlists to restrict what can run.

Plugins on OpenClaw.rocks

On OpenClaw.rocks, your instance comes pre-configured with the messaging channel plugins for Telegram, Discord, WhatsApp, and Signal. You do not need to install or configure these manually. If you need additional plugins for your self-hosted deployment, you can manage them through the OpenClaw CLI.

Learn more