Architecture

What Is OpenClaw Plugin SDK?

A development kit for building custom plugins that extend OpenClaw agent capabilities with new tools, integrations, and behaviors.

In Plain English

The Plugin SDK lets you extend OpenClaw beyond its built-in capabilities. Build custom MCP servers, add new tool integrations, create specialized agent behaviors, and package them as reusable plugins.

Plugins follow the MCP standard, so anything you build works with any MCP-compatible agent — not just OpenClaw. The SDK provides helpers for authentication, error handling, input validation, and testing.

Common plugin use cases: connecting internal APIs, adding industry-specific tools, building custom approval workflows, and integrating with proprietary systems that have no public MCP server.

Why It Matters for OpenClaw

Every organization has unique tools and workflows. The Plugin SDK means you are not limited to pre-built integrations. Extend your agent to work with any system in your stack.

How Clawctl Helps

Clawctl deploys custom plugins alongside your agent. Plugins run in the same sandbox with the same security controls. The dashboard shows plugin health and tool call metrics.

Try Clawctl — 60 Second Deploy

Common Questions

What languages does the SDK support?

TypeScript and Python are the primary supported languages. Any language that can serve HTTP/stdio can work with MCP.

Do plugins get the same security controls?

Yes. Plugins run inside the agent sandbox with the same egress filtering, audit logging, and approval workflows.

Can I share plugins?

Yes. Plugins follow the open MCP standard and can be shared publicly or within your organization.