How do I install the Openclaw MCP skill?

Run npx skillmds@latest add nickgallick/openclaw-mcp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Openclaw MCP skill do?

Skill: OpenClaw MCP Integration It is listed under AI & ML on SkillMD.

Is Openclaw MCP safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openclaw MCP?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openclaw MCP free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openclaw MCP?

nickgallick (@nickgallick) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openclaw MCP by nickgallick — Agent Skill

Name: Openclaw MCP
Author: nickgallick

File contents

Skill: OpenClaw MCP Integration

Changelog

2026-03-19: Initial creation

Overview

MCP (Model Context Protocol) integration knowledge for OpenClaw. Our setup uses mcporter bridge exclusively — NOT native mcpServers.

CRITICAL RULE

NEVER add mcpServers to openclaw.json — This key is not in the Zod schema and will crash the gateway on startup. All MCP configuration goes through the mcporter bridge.

Architecture

OpenClaw Gateway
  └── mcporter bridge (MCP proxy)
        ├── Brave Search MCP
        ├── Filesystem MCP
        └── Other MCP servers

mcporter Bridge

mcporter acts as a bridge between OpenClaw and MCP servers. It:

Runs as a separate process/service
Exposes MCP tools to OpenClaw agents
Handles MCP protocol translation
Manages MCP server lifecycle

mcporter Configuration

mcporter has its own configuration file, separate from openclaw.json.

# Check mcporter status
docker exec openclaw-okny-openclaw-1 ps aux | grep mcporter

# mcporter logs
docker logs openclaw-okny-openclaw-1 2>&1 | grep -i mcporter

Available MCP Tools

Brave Search

Provides web search capability
Used by Scout agent for research
Requires BRAVE_API_KEY environment variable

Filesystem

Provides file read/write/list capabilities
Scoped to specific directories for security

Adding New MCP Servers

Configure in mcporter (NOT openclaw.json)
Restart the mcporter bridge
Verify tools appear in agent capabilities
Test with a simple query

Troubleshooting MCP

# Check if MCP tools are loaded
docker logs openclaw-okny-openclaw-1 2>&1 | grep -i -E "mcp|tool|mcporter"

# Check for MCP errors
docker logs openclaw-okny-openclaw-1 2>&1 | grep -i -E "mcp.*error|tool.*error"

# Verify Brave API connectivity
docker exec openclaw-okny-openclaw-1 curl -s -o /dev/null -w "%{http_code}" "https://api.search.brave.com/res/v1/web/search?q=test" -H "X-Subscription-Token: test"

stitch-mcp

Package: @_davideast/stitch-mcp Purpose: Stitches multiple MCP servers together into a unified interface. Used with mcporter for combining MCP server capabilities.

Common MCP Issues

Tools not appearing → Check mcporter is running and configured correctly
Search failing → Verify BRAVE_API_KEY is set and valid
Timeout errors → MCP server may be overloaded or network issue
"mcpServers not recognized" → Someone added mcpServers to openclaw.json. Remove it immediately and use mcporter instead

---name: openclaw-mcpdescription: Skill: OpenClaw MCP Integration---# Skill: OpenClaw MCP Integration## Changelog- 2026-03-19: Initial creation## OverviewMCP (Model Context Protocol) integration knowledge for OpenClaw. Our setup uses mcporter bridge exclusively — NOT native mcpServers.## CRITICAL RULE**NEVER add `mcpServers` to openclaw.json** — This key is not in the Zod schema and will crash the gateway on startup. All MCP configuration goes through the mcporter bridge.## Architecture```OpenClaw Gateway └── mcporter bridge (MCP proxy) ├── Brave Search MCP ├── Filesystem MCP └── Other MCP servers```## mcporter Bridgemcporter acts as a bridge between OpenClaw and MCP servers. It:- Runs as a separate process/service- Exposes MCP tools to OpenClaw agents- Handles MCP protocol translation- Manages MCP server lifecycle### mcporter Configurationmcporter has its own configuration file, separate from openclaw.json.```bash# Check mcporter statusdocker exec openclaw-okny-openclaw-1 ps aux | grep mcporter# mcporter logsdocker logs openclaw-okny-openclaw-1 2>&1 | grep -i mcporter```## Available MCP Tools### Brave Search- Provides web search capability- Used by Scout agent for research- Requires BRAVE_API_KEY environment variable### Filesystem- Provides file read/write/list capabilities- Scoped to specific directories for security## Adding New MCP Servers1. Configure in mcporter (NOT openclaw.json)2. Restart the mcporter bridge3. Verify tools appear in agent capabilities4. Test with a simple query## Troubleshooting MCP```bash# Check if MCP tools are loadeddocker logs openclaw-okny-openclaw-1 2>&1 | grep -i -E "mcp|tool|mcporter"# Check for MCP errorsdocker logs openclaw-okny-openclaw-1 2>&1 | grep -i -E "mcp.*error|tool.*error"# Verify Brave API connectivitydocker exec openclaw-okny-openclaw-1 curl -s -o /dev/null -w "%{http_code}" "https://api.search.brave.com/res/v1/web/search?q=test" -H "X-Subscription-Token: test"```## stitch-mcpPackage: `@_davideast/stitch-mcp`Purpose: Stitches multiple MCP servers together into a unified interface. Used with mcporter for combining MCP server capabilities.## Common MCP Issues1. **Tools not appearing** → Check mcporter is running and configured correctly2. **Search failing** → Verify BRAVE_API_KEY is set and valid3. **Timeout errors** → MCP server may be overloaded or network issue4. **"mcpServers not recognized"** → Someone added mcpServers to openclaw.json. Remove it immediately and use mcporter instead

Frequently asked questions

Openclaw MCP