get_prompt
Get a specific prompt by ID or name
LABSCO SUMMARY
The prompt library stops being a browser tab.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command plus a key — npx -y @promptz/mcp, then supply credentials
USE CASES
01
Using a prompt you saved earlier
Search the library by tag, then fetch the one you meant by name and apply it to what you are working on.
02
Finding out what is in the library at all
List prompts and rules by tag and page through them, rather than opening the site to browse.
03
Applying a team convention to a project
Fetch the named project rule and let your editor's rule tooling add it to the workspace.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_rule
Get a specific project rule by name
list_prompts
List available prompts from promptz.dev
list_rules
List available project rules from promptz.dev
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. The server only reads prompts and rules; adding a rule to your workspace happens through your editor's own tools.
Requires
- npx on PATH
- PROMPTZ_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @promptz/mcpMCP Clients
Amazon Q Developer
AMAZON Q DEVELOPER · JSON
{
"mcpServers": {
"promptz.dev": {
"command": "npx",
"args": [
"-y",
"@promptz/mcp"
],
"env": {
"PROMPTZ_API_URL": "<YOUR_PROMPTZ_API_URL>",
"PROMPTZ_API_KEY": "<YOUR_PROMPTZ_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}Any MCP client — local build
Clone the repository, install dependencies and build
ANY MCP CLIENT — LOCAL BUILD · TERMINAL
git clone https://github.com/cremich/promptz-mcp.git
cd promptz-mcp
npm install
npm run buildAdd this to your MCP client's settings file
<YOUR_PATH_TO_PROMPTZ_MCP> is the full path of your clone, and <YOUR_PROMPTZ_API_URL> and <YOUR_PROMPTZ_API_KEY> are the API URL and key from your promptz.dev MCP settings page.
ANY MCP CLIENT — LOCAL BUILD · JSON
{
"mcpServers": {
"promptz.dev": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROMPTZ_MCP>/build/index.js"
],
"env": {
"PROMPTZ_API_URL": "<YOUR_PROMPTZ_API_URL>",
"PROMPTZ_API_KEY": "<YOUR_PROMPTZ_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}
