Coven-native MCP server for filesystem and web operations
coven-reach provides 6 well-structured filesystem and utility tools with complete JSON schemas and clear descriptions. Tool names follow verb_noun convention (reach_read, reach_write, reach_list, reach_find, reach_familiar, reach_secret_check). Schemas are present and typed for all tools. However, parameter descriptions are sparse or missing in several tools (reach_write entries/archive_path lack detail), and output schemas are not documented. Error handling guidance is absent, tools do not indicate what to do on failure. reach_write lacks confirmation/dry-run patterns for destructive operations. Overall solid foundation but missing LLM-optimization details and recovery guidance.
List OpenCoven familiars from ~/.openclaw/workspace. Returns name, creature, vibe, workspace path, session count, and memory status for each familiar. Read-only, no credentials required.
Advanced file search with glob patterns, content search (text/regex), size/date filters, and MIME type filtering.
List directory contents or get server/system info. Operations: entries (directory listing with optional recursion and size calculation), system_info (server capabilities, config).
Read files or fetch URLs. Operations: content (read file/URL as text, base64, or markdown), metadata (stat/HEAD), diff (unified diff between two files), checksum (sha256/sha512/md5). Supports batch sources array.
Scan files or directories for common secret patterns (API keys, tokens, private keys). Reports file:line locations only — secret values are NEVER included in output. Useful for pre-commit checks.
Filesystem write operations. Operations: put (write file), mkdir, copy, move, delete, touch, archive (zip/tar.gz), unarchive. Disabled when COVEN_REACH_READ_ONLY=true.
reach_write lacks confirmation/dry-run pattern for destructive operations (delete, move, unarchive). Agents can accidentally destroy data without a safety gate.
Output schemas not documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what does reach_find return? file paths? metadata? counts?).
reach_write 'entries' parameter lacks description. What structure does it expect? Array of {path, content}? {source, dest}? Ambiguous parameter forces LLM to guess.
No error handling guidance. Tools do not indicate retryable vs fatal errors, or what the LLM should do on failure (e.g., 'File not found, try reach_find() first').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
reach_familiar description is vague ('List OpenCoven familiars'). Does not explain when to call it or what a 'familiar' is in context. Unclear use case.