Prompt Manager

Created By
appositeita year ago
A web and API-based system for managing, composing, and organizing AI prompts, with an MCP server for intetgration with common AI pltforms (Claude Desktop, Cursor, Windsurf, etc.).
Overview

what is Prompt Manager?

Prompt Manager is a web and API-based system designed for managing, composing, and organizing AI prompts, facilitating integration with common AI platforms like Claude Desktop and Cursor.

how to use Prompt Manager?

To use Prompt Manager, clone the repository, set up the environment, and run the application. Access the web interface at http://localhost:8081 or use the RESTful API for programmatic management of prompts.

key features of Prompt Manager?

  • Create and manage both standard and composite prompts.
  • Compose templates with prompt inclusions and expansions.
  • Real-time editing via WebSocket.
  • Access prompts through a RESTful API.
  • Organize prompts in directories and integrate with Model Context Protocol (MCP).

use cases of Prompt Manager?

  1. Managing AI prompts for various applications.
  2. Composing complex prompt templates for AI interactions.
  3. Real-time collaboration on prompt editing.

FAQ from Prompt Manager?

  • Can I use Prompt Manager without coding?

Yes! You can use the web interface for managing prompts without any coding.

  • Is there an API available?

Yes! Prompt Manager provides a RESTful API for programmatic access to prompt management.

  • How do I integrate with other AI platforms?

Prompt Manager supports integration with platforms like Claude Desktop through the Model Context Protocol (MCP).

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
appositeit
Star
0
Language
Python
License
View license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago