Files

T

History

EmerikoandClaude Opus 4.8 e181b89ac0 chore(ponytail-mcp): mark private, drop dead bin

ponytail-mcp reuses the repo's hooks/ via createRequire("../hooks/..."), which
reaches outside the package dir, so it can only run from a checkout (as its
README says), never as a published npm package — a publish tarball wouldn't
include ../hooks/ and would crash. The `bin` field and missing `private` made
it look publishable. Mark it private so an accidental `npm publish` can't ship
a broken package, and drop the dead bin (you point the host at ponytail-mcp/index.js).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-19 01:56:56 +02:00

test

feat(mcp): add ponytail-mcp, an MCP server for the ruleset (#91 )

2026-06-19 00:24:40 +02:00

index.js

feat(mcp): add ponytail-mcp, an MCP server for the ruleset (#91 )

2026-06-19 00:24:40 +02:00

instructions.js

feat(mcp): add ponytail-mcp, an MCP server for the ruleset (#91 )

2026-06-19 00:24:40 +02:00

package.json

chore(ponytail-mcp): mark private, drop dead bin

2026-06-19 01:56:56 +02:00

README.md

feat(mcp): add ponytail-mcp, an MCP server for the ruleset (#91 )

2026-06-19 00:24:40 +02:00

README.md

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. Optional mode argument: lite, full, or ultra. Omit it to use the configured default.
Tool ponytail_instructions — same text, plus structuredContent ({ 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.