Skip to main content
Glama
aidevelopers2

remoteopenclaw-mcp

README.md
# Remote OpenClaw MCP Server

An MCP server that lets any AI agent — **Claude Code, OpenClaw, Hermes, Codex, Cursor** — search [Remote OpenClaw](https://www.remoteopenclaw.com) directly from your editor: a directory of **13,870+ MCP servers, 4,384+ agent skills, and plugins**.

Instead of opening a browser to find a tool, your agent can just search the directory for you and hand back install commands.

## Tools

| Tool | What it does |
|---|---|
| `search_mcp_servers` | Find an MCP server for a task (databases, scraping, GitHub…) |
| `search_skills` | Find a reusable agent skill, with its install command |
| `search_plugins` | Find a plugin / marketplace package |

Each returns names, descriptions, links, and popularity, ranked by stars or installs.

## Install

Add it to your MCP client config (no API key needed):

```json
{
  "mcpServers": {
    "remoteopenclaw": {
      "command": "npx",
      "args": ["-y", "remoteopenclaw"]
    }
  }
}
```

- **Claude Code:** add the block above to `~/.claude.json` (or run `claude mcp add remoteopenclaw -- npx -y remoteopenclaw`)
- **Cursor / Windsurf / other MCP clients:** add the same block to your MCP settings

## Usage

Ask your agent things like:

- *"Find me an MCP server for Postgres."*
- *"Search Remote OpenClaw for a PDF skill."*
- *"What plugins are there for testing?"*

Your agent calls the matching tool, searches the directory, and returns the top results with links and install commands.

## How it works

A thin wrapper over the public Remote OpenClaw search API (`https://www.remoteopenclaw.com/api/search`), so results are always live and the package stays tiny. Built with the [Model Context Protocol](https://modelcontextprotocol.io) TypeScript SDK.

## License

MIT

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct target (MCP servers, plugins, skills), with clear descriptions that leave no ambiguity. An agent can easily differentiate them.

Naming Consistency5/5

All tools follow the exact same pattern: 'search_' followed by the plural noun of the target resource (servers, plugins, skills). This is perfectly consistent.

Tool Count5/5

Three tools is appropriate for a focused search-oriented server. Each tool covers a distinct category and is justified by the directory size mentioned.

Completeness4/5

The server covers the main asset types listed (servers, plugins, skills). There are no obvious gaps given its stated purpose; however, it might miss other potential resources like 'agents' or 'clients', but that's minor given the description.

Maintenance

ActivityStale
ResponsivenessNo issues