One subscription gives you access to a curated set of production-ready MCP servers. No need to find, build, or maintain them yourself.
ServerPurposeAccessfilesystem-secureFile system access with sandbox (chroot)Read/write within allowed rootsmemory-enhancedMemory server with WAL + compaction survivalPersistent JSON storegithubGitHub API integration (issues, PRs, repos, search)Requires GitHub tokenpostgresPostgreSQL read-only queriesRequires DB connection stringwebsearchWeb search via DuckDuckGo + BraveNo API key neededrssRSS/Atom feed aggregatorPublic feeds
mcp configdocker-compose.yml and manages lifecyclejson
{}
Returns list of available servers with status (cloud_available, self_hosted_available, description).
json
{
"servers": ["filesystem-secure", "github"]
}
Returns OpenClaw mcp configuration JSON:
json
{
"mcp": {
"servers": {
"filesystem-secure": {
"command": "docker",
"args": ["run", "-i", "--rm", "-v", "/path/to/allowed:/data", "openclaw/mcp-filesystem-secure"]
},
"github": {
"transport": "stdio",
"command": "npx",
"args": ["-y", "mcp-github"],
"env": {"GITHUB_TOKEN": "..."}
}
}
}
}
Cloud includes:
Q: Can I mix cloud and self-hosted?
A: Yes. Use mcp_config_generate to get configs for hybrid setups.
Q: Is data sent to cloud?
A: For cloud servers yes, but encrypted in transit (TLS). For filesystem, your data stays local unless you mount remote volumes.
Q: How do I get a GitHub token for github server?
A: Create a fine-grained PAT with issues:read, pull_requests:read, repo:status scopes.
Q: Can I add my own MCP servers?
A: Yes, the skill supports custom entries via mcp_config_append.
This pack turns MCP from a curiosity into a production integration platform.