list_componentsLABSCO SUMMARY
Your saved prompts become something you can ask for by name.
Instead of pasting a persona in at the start of every session, the assistant fetches it — and a pack arrives with its components already resolved, so a multi-part setup is one call rather than four.
What it is
A read path into a Prompt Builder account: the components you have saved — personas, protocols, formats, templates — plus the community packs that bundle them.
What you get
- Components listed by type: persona, protocol, format or template
- One component's full content, fetched by ID
- Components found by name
- Community packs listed by category
- A complete pack with every component in it already resolved
Requirements
Node.js 18 or newer, the package installed globally, and a Prompt Builder API key generated in your account settings and passed on the launch command.
Setup effort
One command plus a key — npm install -g promptbuilder-mcp, then supply credentials
USE CASES
Starting a session in the right voice
Name the persona and it is loaded from your vault, identical to the last time you used it.
Finding the protocol you wrote months ago
List by type or search by name, rather than scrolling a settings page to find the one you mean.
Loading a whole working setup at once
A pack comes back with its components resolved, so persona, protocol and format arrive together.
Seeing what is in your vault
The inventory of components and packs, read from the conversation where you would otherwise be guessing.
5 tools
Listed in project docs. Your client may show a different list.
get_componentsearch_componentslist_packsget_packBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- promptbuilder-mcp on PATH
- Node.js 18+
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
npm install -g promptbuilder-mcpMCP Clients
Claude Desktop, Cursor
{
"mcpServers": {
"promptbuilder": {
"command": "promptbuilder-mcp",
"args": [
"--key",
"<YOUR_API_KEY>"
]
}
}
}