Four read-only calls, and the whole value is removing the round trip: ask for the prompt about React component documentation by name and it arrives in the session where the code already is. Rules work the same way and are the more interesting half — a project rule fetched here can be handed to whatever writes rules into your workspace, so a shared convention lands in a repository without anyone retyping it.
A read-only client for promptz.dev. Prompts and project rules stored there are listed and fetched by name, so the assistant can use one directly rather than waiting for you to paste it in.
- The prompt library listed, filtered by tags and paged with a cursor when it is long
- A single prompt fetched by name, ready to be applied to the code in front of you
- Project rules listed the same way, by tag and page
- A named project rule fetched so it can be added to the workspace by whatever tool manages your rules
An API URL and API key from the promptz.dev MCP settings page, supplied as PROMPTZ_API_URL and PROMPTZ_API_KEY. It runs over stdio as npx -y @promptz/mcp. Access is read-only — there is no write path, so nothing here can change your library. Traffic to the promptz.dev API goes over HTTPS, and the server writes a log to ~/.promptz/logs/mcp-server.log in your home directory.
One command plus a key — npx -y @promptz/mcp, then supply credentials