openclaw vs Grain SQL
openclaw is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Grain SQL is an MCP server published by pattrnlabs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace daymade/claude-code-skills | Listed Version: 1.3.0 Forks (GitHub): 228 Stars (GitHub): 1 480 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.35 Downloads/month (npm): 5 377 Downloads/week (npm): 506 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.10.35 Downloads/month (npm): 5 377 Downloads/week (npm): 506 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | openclaw | Grain SQL |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 480 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 228 (better) | 1 (worse) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (grain-tools) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/daymade/claude-code-skills | github.com/pattrnlabs/grain |
| Changes in the last 7 days (differs) | 2 | 8 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
openclaw
Manage OpenClaw (龙虾 / lobster) instance configurations, gateway health, and plugin lifecycle — audit, diff, copy, add-model, list, and switch models across openclaw.json files; diagnose a parked or down gateway, plugin register failures, and hooks blocked after an upgrade; confirm whether an install is out of date. Use when juggling multiple OpenClaw / Claude Code wrapper instances, applying DeepSeek model patches, managing default models and aliases, or validating config.
Grain SQL
Run SQL queries and inspect database schemas through safe, visible MCP tools.
How to run each
openclaw As a Claude Code plugin
/plugin marketplace add daymade/claude-code-skills
/plugin install openclaw@daymade-skills
Grain SQL As a local MCP server: npm package
claude mcp add --env "GRAIN_CONNECTIONS=<YOUR_GRAIN_CONNECTIONS>" --transport stdio grain -- npx -y grain-tools
Requires: GRAIN_CONNECTIONS (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of openclaw publish no settings it asks for, so we do not compare settings.
What it can do: openclaw · What it can do: Grain SQL · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.