emin-mcp

Emin's portable rules + tooling instructions as an MCP server. One server, every MCP client (opencode, Claude Code, Cursor, Continue, ...).

What it exposes

Two resources, no tools (yet — YAGNI):

• rules://emin/global — Emin's global working rules (never invent features, TLDR first, complexity check, etc.)

• rules://emin/tooling — mandatory tooling instructions (ponytail ultra + nuanced MCP)

The server instructs, it does not wrap. Ponytail stays an opencode plugin; nuanced stays its own MCP server. This server tells every agent to use them.

Related MCP server: agent-rules-mcp

Install

npm install

Run

npm start

Wire into a client

opencode.json

{
  "mcp": {
    "emin": {
      "type": "local",
      "command": ["node", "/path/to/emin-mcp/src/index.mjs"],
      "enabled": true
    }
  }
}

Claude desktop_config.json

{
  "mcpServers": {
    "emin": { "command": "node", "args": ["/path/to/emin-mcp/src/index.mjs"] }
  }
}

Selfcheck

npm run selfcheck

Proves the server boots and both resources serve the expected content. No test framework, just assertions.

Why an MCP server and not a CLAUDE.md / AGENTS.md

• Portable across every MCP client, not just one harness.

• One source of truth — edit here, every project picks it up.

• Room to grow: add enforcement tools (scope_check, logbuch) later without changing the transport.