Ashlr Plugin MCP Server

Connect Ashlr Plugin to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Multi-host AI coding efficiency layer for Codex and Claude Code, powered by @ashlr/core-efficiency. The ashlr plugin mcp server is what makes that connection.

What the server does

40 MCP tools that replace high-volume Read / Grep / Edit / Bash workflows with versions that return less without losing what matters. Claude Code gets automatic PreToolUse redirects (ASHLR_HOOK_MODE=redirect); Codex gets first-class plugin packaging, MCP, skills, and nudge-first hooks.

Credentials and setup notes

Configuration is passed through the environment: ASHLR_MCP_HOST, ANTHROPIC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by ashlrai; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Ashlr Plugin's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.