Prompt Saver - LLM Prompt Intelligence Platform

Live: https://promptsaver.online/

Chrome extension: Add to Chrome — type // in Claude, ChatGPT or Gemini to insert a saved prompt.

A prompt management tool for saving, versioning, and searching LLM prompts. Built with Next.js, Neon Postgres, and a warm stone/teal design system.

Features (MVP - Phase 1)

• Prompt Authoring: Create and edit prompts with automatic versioning
• Multi-LLM Testing: Execute prompts against multiple LLM providers from a single interface
• Prompt Library: Full-text search and intelligent categorization of prompts
• Workspace-Based Organization: Organize prompts within dedicated workspaces

MCP Server (Claude Code Integration)

Prompt Saver runs a remote MCP server at /api/mcp, so a Claude Code session can search, read, and save your prompts without leaving the terminal.

Connect

1. Sign in at https://promptsaver.online/, then click Settings and generate a token. The raw token is shown exactly once — copy it immediately. Only its SHA-256 hash is stored, so a lost token can't be recovered; revoke it on the same page and create a new one.

2. The tokens page shows the registration command with your token filled in. It looks like:

   claude mcp add --transport http prompt-saver --scope user \
     https://promptsaver.online/api/mcp \
     --header "Authorization: Bearer ps_..."
   

   --scope user registers the server once for every project rather than just the current one.

Tools

Once connected, Claude Code can call five tools against your prompt library:

• search_prompts(query, limit?) — searches title, description, content and tags. Returns summaries only (id, title, description, tags, updated_at) — never full bodies. limit defaults to 20 and is capped at 50.
• get_prompt(id) — fetches the full text of one prompt.
• create_prompt(title, content, description?, tags?) — saves a new prompt along with its first version.
• update_prompt(id, ...) — updates a prompt's draft in place, without creating a new version.
• save_version(id, content, change_summary?) — saves an immutable new version of an existing prompt.

There is no delete tool.

Favourite prompts as slash commands

Any prompt marked as a favourite (the star in the web app) is also registered as a slash command, named from its title — "Daily Planning" becomes /mcp__prompt-saver__daily-planning. Archived favourites are excluded. Each command takes one optional context argument, appended to the prompt body:

/mcp__prompt-saver__daily-planning auth refactor

Favourites are read once, when the session connects. Starring a prompt does not add its slash command to a session that's already running — open a new session, or run /mcp to reconnect, to pick up newly starred prompts.

Cold starts

The database backing this app (Neon Postgres) scales its compute to zero when idle. The first MCP request after a period of inactivity may take noticeably longer while it wakes back up; subsequent requests are fast.

Chrome extension

The Chrome extension lives in extension/. It lets users save prompts from any webpage or AI chat interface.

Setup and development

cd extension
npm install
npm run dev

The development build is unpacked and ready to load into Chrome. Configuration requires the web app's NEXT_PUBLIC_EXTENSION_IDS environment variable to contain the extension's ID (visible in chrome://extensions/ when unpacked). Set it to * to allow any well-formed extension ID. That's useful while unpacked IDs change, but any extension can then ask a signed-in user to connect (the connect page shows the requesting ID), so use an explicit list in production.

API

The extension calls these endpoints on the web app's /api/v1/prompts route:

Method	Path	Purpose	Headers
GET	/api/v1/prompts	List prompts. Accepts ?q=<query>&limit=<n> (limit ≤200).	Authorization: Bearer ps_<token>
POST	/api/v1/prompts	Create a new prompt.	Authorization: Bearer ps_<token>
GET	/api/v1/prompts/:id	Fetch a single prompt by ID.	Authorization: Bearer ps_<token>
PATCH	/api/v1/prompts/:id	Update a prompt.	Authorization: Bearer ps_<token>

All endpoints require a bearer token prefixed with ps_.

For privacy details, see /privacy.

Technology Stack

• Frontend: Next.js 16, React 18, TypeScript (strict mode)
• Styling: Tailwind CSS (WCAG 2.1 AA accessible)
• Storage: Neon Postgres via Drizzle ORM (server-side, per-user isolated)
• Authentication: Google OAuth via NextAuth.js
• Testing: Jest + React Testing Library
• Code Quality: ESLint, Prettier, TypeScript strict mode

Prerequisites

• Node.js 18.17+ or 20.x
• npm 9+ (or use npm ci with --legacy-peer-deps)

Setup

1. Clone and Install

git clone <repository-url>
cd prompt-saver
npm install --legacy-peer-deps

2. Configure Environment Variables

Create .env.local based on .env.example:

cp .env.example .env.local

Required variables:

NEXTAUTH_SECRET=your-secret-key-here
NEXTAUTH_URL=http://localhost:3000
GOOGLE_CLIENT_ID=your-google-client-id
GOOGLE_CLIENT_SECRET=your-google-client-secret
DATABASE_URL=postgresql://...-pooler.../neondb?sslmode=require
DATABASE_URL_UNPOOLED=postgresql://.../neondb?sslmode=require
[email protected]

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗