plugmyagent

Connect your first
MCP server.

MCP servers are plug-ins that give your agent new abilities: reading web pages, searching docs, querying databases. This walkthrough adds one server to OpenClaw in under five minutes. No API keys needed.

Guides/Setup/W03

Goes with guide 002, section 03 (Connect your world). This is that section, hands-on.

Prerequisite: OpenClaw installed and running. Not there yet? Do walkthrough W02 first.

What you end up with

MCP plug-ins on your OpenClaw agent. This is Track B, part 2 of 2, and it only applies to the OpenClaw agent from W02. On the phone track? Guide 004 connects APIs to any agent instead.

01Add the Fetch server with one command

Fetch is maintained by the MCP team and gives your agent one new ability: fetch any web page and read it as clean text. It needs no API key and no settings beyond its name.

openclaw mcp set fetch '{"command":"npx","args":["-y","@modelcontextprotocol/server-fetch"]}'

Reading that command: the server is named fetch, it launches with npx, and the -y flag lets npx download the official package automatically.

What success looks like

Run openclaw mcp list. You see fetch in the list. It is registered.

02Confirm it loaded

openclaw mcp show fetch --json
What success looks like

You see the server's details and its fetch tool. Your agent can now call it.

03Ask your agent to use it

Open your OpenClaw dashboard and send this:

Copy, paste, send

"Fetch https://example.com and tell me what it says."

What success looks like

Your agent returns a summary of the page instead of saying it cannot browse. That is your first MCP-powered answer.

04Understand what you just configured

Every MCP server is one entry under mcp.servers in OpenClaw's config file (~/.openclaw/openclaw.json). Two shapes cover almost everything:

Local server: launched on your machine
{
  "mcp": {
    "servers": {
      "fetch": {
        "command": "npx",
        "args": ["-y", "@modelcontextprotocol/server-fetch"]
      }
    }
  }
}
Remote server: runs somewhere else, key in headers
{
  "mcp": {
    "servers": {
      "docs": {
        "url": "https://mcp.example.com",
        "transport": "streamable-http",
        "headers": { "Authorization": "Bearer YOUR_KEY_HERE" }
      }
    }
  }
}

The CLI writes this config for you, so you rarely edit the file by hand. One rule from the official docs: never put real secrets inline in the config. Use an environment variable like ${MY_API_KEY} and export it before starting the gateway.

The pattern

Pick a server, run openclaw mcp set, check openclaw mcp list, test it. That is the whole skill. Every future server works the same way.

05Find your second server

Browse the plugmyagent MCP directory: 34 free servers, every one verified, each with copy-paste config. Pick one that solves a problem you actually have.

MCP

The MCP server directory

34 genuinely free MCP servers with install commands, copy buttons, and category search. Find your next plug-in.

Free · Verified · Copy-paste configs

When something goes wrong

The first run hangs for a minute

npx is downloading the package the first time. Give it a minute on a decent connection. It is instant on every run after that.

The server is listed but the agent says it cannot use it

Start a fresh session so the agent picks up the new tools. If it persists, run openclaw mcp show fetch --json and read the error it reports.

I want to remove a server 
openclaw mcp unset fetch

Then openclaw mcp list to confirm it is gone.