EmerikoandClaude Opus 4.8
426ffd0b36
Em dashes crept back into examples, docs/platform-native.md, several READMEs,
the ponytail-debt skill, and a command file since 88431de. Replaced with plain
punctuation (commas, matching the house convention), .openclaw mirror
regenerated. Follows 88431de's scope: leaves untouched the vendored caveman
SKILL.md and the dated benchmarks/results/ writeups (historical records).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.5 KiB
ponytail-mcp
An MCP server that serves Ponytail's lazy-senior-dev instructions. It exposes the same ruleset the Claude hooks and Pi extension use, so every host emits identical rules.
It is not a replacement for the always-on adapters. Ponytail normally lives in the system context every turn. MCP prompts are user-invoked, and there is no portable MCP primitive for "inject this into every turn" across hosts. So this server is the clean option for MCP hosts whose only injection point is the prompt menu, or that pull context through tools. See issue #70.
What it exposes
- Prompt
ponytail, returns the ruleset as a user message. Optionalmodeargument:lite,full, orultra. Omit it to use the configured default. - Tool
ponytail_instructions, same text, plusstructuredContent({ mode, instructions }), for hosts that pull context via tools or code execution. Read-only.
Mode resolution reuses hooks/ponytail-config.js, so PONYTAIL_DEFAULT_MODE
and ~/.config/ponytail/config.json work the same as everywhere else.
Run it
cd ponytail-mcp
npm install
node index.js # speaks MCP over stdio
Point an MCP host at that command. Example client entry:
{ "mcpServers": { "ponytail": { "command": "node", "args": ["ponytail-mcp/index.js"] } } }
Test
npm test
Covers mode resolution and the instruction text. The MCP wiring in index.js
is intentionally thin: it just maps the prompt and tool onto
buildInstructions.