Prompt Book Server
OfficialAllows managing AI prompts stored in Notion databases, including search, retrieval, addition, updating, and copying of prompts across multiple prompt collections.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Prompt Book Server list all prompts in my active book"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Prompt Book Server
An MCP server that connects to Notion databases containing AI prompts, allowing you to manage, search, and retrieve prompts efficiently across multiple prompt collections.
What does prompt book server do?
The Prompt Book Server is a powerful tool that helps you organize and access your AI prompts stored in Notion databases. It provides the following key capabilities:
Multiple Prompt Books: Manage multiple collections of prompts (prompt books) with different Notion databases
Prompt Discovery: Search, filter, and browse prompts by title, type, or tags
Prompt Retrieval: Quickly access the full content of any prompt
Prompt Management: Add new prompts, update existing ones, and copy prompts between books
Database Creation: Create new prompt databases with the proper schema directly in Notion
The server acts as a bridge between your AI tools and your Notion-based prompt collections, making it easy to maintain a centralized library of prompts that can be accessed from various coding and AI tools.
Related MCP server: Notion MCP Server
All the tools
Configuration Management Tools
Tool Name | Description |
| Lists all configured prompt books |
| Adds a new prompt book configuration |
| Removes a prompt book configuration |
| Sets a prompt book as active |
| Renames a prompt book configuration |
| Creates a new prompt database in Notion and adds it to the configuration |
| Copies a prompt from one book to another |
Prompt Management Tools
Tool Name | Description |
| Lists all prompts in the active database |
| Searches prompts by title |
| Gets prompts filtered by a specific tag |
| Gets prompts filtered by a specific type |
| Reads the full content of a specific prompt |
| Lists all unique prompt types in the database |
| Lists all unique tags used in the database |
| Adds a new prompt to the database |
| Updates an existing prompt in the database |
How to configure it in my coding tools (or non coding tools)?
Add to MCP Configuration
Add the server to your MCP configuration file. The location depends on your MCP client:
Path to the MCP config
cline:
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.jsonroo_code:
~/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.jsonwindsurf:
~/.codeium/windsurf/mcp_config.jsonclaude:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the following configuration:
{
"mcpServers": {
"prompt-book-server": {
"command": "npx",
"args": [
"-y",
"@piccollage/prompt-book-mcp-server"
],
"disabled": false,
"alwaysAllow": []
}
}
}Example prompts to work with it
Here are some example prompts you can use to interact with the Prompt Book Server:
Listing and Searching Prompts
List all my prompt books.Show me all prompts in the prompt book.Search for prompts related to "GPUImage" in my prompt book.Show me all prompts with the tag "PicCollage".List all prompts of type "Coding"What types of prompts are available in my prompt book?Reading Prompts
Get the prompt about idea evaluation from the prompt book.
Follow the instructions in it and then verify the following idea for me:
describe your ideaManaging Prompt Books
Activate the engineering prompt book.Copy the GPUImage porting prompt from my private book to the engineering book.Adding and Updating Prompts
Add a new prompt titled "React Component Generator" with type "Coding" and tags ["React", "Frontend"].
The prompt should include ....
......
.....Update the "React Component Generator" prompt to include TypeScript support.Please create a very detailed prompt to instruct LLM agents to convert Android XML UI implementations into Compose UI elements or screens. Put that prompt to the prompt book.How to add a new prompt book?
You have two main options for adding a new prompt book:
Option 1: Connect to an Existing Notion Database
If you already have a Notion database with prompts, you can connect it directly:
Get your Notion API token from https://www.notion.so/my-integrations
Share your Notion database with your integration
Get the database ID from the URL (it's the part after the workspace name and before the question mark)
Use the
create_prompt_book_configtool:
Add a new prompt book with the following details:
- Name: "My Team Prompts"
- Notion token: "secret_abc123..."
- Notion database ID: "1a748be2b63280988d9bc5f89918431d"Option 2: Create a New Notion Database
If you want to create a fresh prompt database with the correct schema:
Get your Notion API token from https://www.notion.so/my-integrations
Find the ID of a Notion page where you want to create the database
Use the
create_prompt_databasetool:
Create a new prompt database with these details:
- Name: "My New Prompt Book"
- Notion token: "secret_abc123..."
- Page ID: "1a748be2b63280988d9bc5f89918431d"
- Activate: trueThis will create a new database with the proper schema (Name, Type, Tags) and add it to your configuration.
Notion Database Requirements
For optimal functionality, your Notion database should have the following properties:
Name (title): The title of the prompt
Type (select): The category of the prompt (e.g., "Coding", "Image Generation")
Tags (multi-select): Tags for organizing and filtering prompts
The prompt content itself is stored in the page body as blocks of text.
Development
Prerequisites
Node.js 16+
TypeScript
Notion API token
Setup
Clone the repository
Install dependencies:
npm installBuild the project:
npm run buildRun the server:
npm start
Configuration File Structure
The configuration file at ~/.mcp_config/prompt_book.json has the following structure:
{
"promptBooks": [
{
"id": "uuid-string",
"name": "My Prompt Book",
"notion_token": "your-notion-api-token",
"notion_database_id": "your-notion-database-id"
}
],
"activePromptBookId": "uuid-string"
}Environment Variable Configuration (DEFAULT_BOOKS)
You can provide a default configuration using the DEFAULT_BOOKS environment variable. This is particularly useful for:
Setting up prompt books automatically in deployment environments
Providing default configurations for team members
Pre-populating the server with prompt book configurations
The DEFAULT_BOOKS environment variable should contain a valid JSON string matching the configuration file structure above.
Important Notes:
The
DEFAULT_BOOKSenvironment variable is only used when the configuration file~/.mcp_config/prompt_book.jsondoesn't exist yetIf the configuration file already exists, the environment variable is ignored
If the JSON in
DEFAULT_BOOKSis invalid or doesn't match the expected structure, it will be ignored and an empty configuration will be created instead
Example usage:
# Set the environment variable
export DEFAULT_BOOKS='{"promptBooks":[{"id":"12345678-1234-1234-1234-123456789012","name":"Default Prompt Book","notion_token":"secret_abc123...","notion_database_id":"1a748be2b63280988d9bc5f89918431d"}],"activePromptBookId":"12345678-1234-1234-1234-123456789012"}'
# Run the server - it will use the DEFAULT_BOOKS configuration if no config file exists
npx @piccollage/prompt-book-mcp-serverThis feature is especially useful when deploying the server in containerized environments or when you want to provide team members with a pre-configured setup.
Available Tools
16 toolsactivate_prompt_bookB
Set a prompt book as active
Inputs: id (required).
add_promptB
Add a new prompt to the database
Inputs: name (required), type (required), detailed_prompt (required), tags.
copy_promptB
Copy a prompt from one book to another
Inputs: prompt_id (required), destination_book_id (required), source_book_id.
create_prompt_book_configC
Add a new prompt book configuration
Inputs: name (required), notion_token (required), notion_database_id (required).
create_prompt_databaseB
Create a new prompt database and add it to the configuration
Inputs: name (required), page_id (required), notion_token (required), activate.
get_prompts_by_tagB
Get prompts by tag
Inputs: tag (required).
get_prompts_by_typeB
Get prompts by type
Inputs: type (required).
list_all_tagsA
List all unique tags used in the database
Inputs: no named parameters.
list_all_typesA
List all unique prompt types in the database
Inputs: no named parameters.
list_prompt_booksA
List all configured prompt books
Inputs: no named parameters.
list_promptsB
List all prompts in the database
Inputs: show_all_fields.
read_promptA
Read the content of a specific prompt
Inputs: prompt_id (required).
remove_prompt_book_configC
Remove a prompt book configuration
Inputs: id (required).
rename_prompt_bookA
Rename a prompt book configuration
Inputs: id (required), name (required).
search_prompts_by_titleC
Search prompts by title
Inputs: query (required).
update_promptC
Update an existing prompt in the database
Inputs: prompt_id (required), name, tags, type, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct entity or action: prompt book configs, prompt databases, individual prompts, and metadata queries. The list/search/get operations are clearly separated by their parameters and descriptions, so there is little risk of selecting the wrong tool.
Most tools follow a consistent verb_noun pattern such as create_prompt_book_config, list_prompts, and rename_prompt_book. The main inconsistency is using both read_prompt and get_prompts_by_* for retrieval, but the overall naming remains predictable.
At 16 tools, the set is slightly above the ideal range, but the domain covers both book configuration management and prompt metadata retrieval. Each tool has a clear purpose, though the number is on the higher end for a single server.
The server covers prompt book lifecycle operations, database creation, and prompt add/update/read/query operations. However, there is no delete or remove prompt tool and no way to remove a prompt database, so lifecycle management is incomplete for the core prompt entity.
Maintenance
Related MCP Connectors
Your versioned prompt library: search, read, save and version prompts from Claude Code.
Manage, version, and publish LLM prompts with blocks, variables, and evaluations.
Your prompt library in any MCP client: list, fetch, save and version prompt templates.
A prompt engineer you talk to. It writes prompts, sharpens yours, and keeps them on your shelf.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Notion workspaces through the Notion API. Supports searching, reading, creating pages, and querying databases with filters and sorting capabilities.5,773 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Notion workspaces through the Notion API, allowing them to search, read, create, update pages and databases, and manage comments using natural language commands.265,848 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search, create, and manage Notion workspace content including pages and databases. It supports advanced database querying, page updates, and content organization through natural language conversations.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Notion databases and pages via the Notion API. Allows searching, reading, and writing to Notion through natural language.MIT