Getting started · config first

OpenClaw MCP quick start: make one server work first

This page is for getting a real MCP server running with the smallest safe config, then knowing exactly where to look when OpenClaw cannot start it.

Last reviewed: 2026-04. Verify against the latest OpenClaw docs before production use.

Who this is for / not for

Good fit

  • First-time OpenClaw + MCP setup
  • Safely exposing one local project folder
  • Fixing invalid JSON, server failed to start, or permission errors

Not a fit

  • Enterprise permission architecture
  • Bypassing OAuth or platform security controls
  • Opening broad local access before deciding what AI may read

Before you paste this config

Create a dedicated workspace folder first. Do not expose your full home directory, filesystem root, desktop dump, SSH keys, cloud credentials, cookies, or production secrets.

Minimal working config

Start with one filesystem server and one relative directory. This keeps OpenClaw inside ./openclaw-workspace while you prove the MCP connection works.

Minimal filesystem config json 
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "./openclaw-workspace"]
    }
  }
}

Safer config

Split real project files from scratch output. The dangerous permissions are root, home, credential folders, production secret folders, and broad write access to places you do not review.

Safer filesystem config json 
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "./openclaw-workspace",
        "./openclaw-scratch"
      ]
    }
  }
}

Verify the MCP server

Create the allowed folders, then check whether OpenClaw sees the server.

Verify MCP server bash 
mkdir -p openclaw-workspace openclaw-scratch
openclaw status

Expected result: OpenClaw should show the filesystem server as loaded. Then ask it to list ./openclaw-workspace. Attempts to read outside the allowed folders should be denied.

⚡️ One-Command Setup

Magic Setup - Zero Config Required

Copy this prompt and paste it into openclaw. It will auto-install 4 essential MCP servers in 30 seconds.

magic-setup.txt 
@OpenClaw (openclaw) I need you to set up my "Super Assistant" environment automatically.

Please follow these steps:

1. [Check Environment]: Verify if Node.js (v18+) is installed. If missing, guide me to install it first.

2. [Install Core MCP Servers]: Use npx to install these essential servers (no API keys needed):
   • @modelcontextprotocol/server-filesystem (Access to Desktop/Documents)
   • @modelcontextprotocol/server-memory (Long-term memory)
   • @modelcontextprotocol/server-fetch (Web scraping)
   • @modelcontextprotocol/server-sequential-thinking (Deep reasoning)

3. [Verify]: After installation, test it: "List files on my Desktop"

Execute step-by-step. If you encounter "command not found", let me know.
✅ No Config Needed
⏱️ 30s Install
🎯 Covers 80% Use Cases
✓ Verified for Claude 3.5 Sonnet
❓ Installation Failed? 🔑 Need More MCPs?

Common errors

command not found

Symptom: OpenClaw or npx is not recognized. Cause: OpenClaw/Node is not installed or PATH is stale. Fix: reopen the terminal and confirm node -v, npx -v, and openclaw status. Ask for review if the shell and app disagree.

invalid JSON

Symptom: OpenClaw fails before the server starts. Cause: trailing comma, bad quote, escaped Windows path, or comments in JSON. Fix: validate the mcpServers block alone. Ask for review when the parser location is unclear.

server failed to start

Symptom: filesystem never reaches running state. Cause: npx cannot fetch the package, package name is wrong, or network policy blocks npm. Fix: run the verify command and check npm access.

path not allowed

Symptom: file reads are rejected. Cause: the requested path is outside the allowed args. Fix: add only the specific project folder you need; never use home or root as the quick fix.

When to ask for review

If you have removed secrets but still cannot tell whether the breakage is JSON, path scope, Node/npm, or OpenClaw config location, send the config snippet and error log for review.

Next step

After the minimal setup works, use the Top 10 list to choose GitHub, search, browser, or database MCPs. Top 10 list.