Mcp Prompt Optimizer (local)

Created By
nivlewd110 months ago
Advanced Local Prompt Intelligence Engine with complete privacy and sophisticated content analysis. Features cross-platform support (Windows, macOS, Linux), binary optimization, and dual-tier processing: AI-aware rules engine + optional LLM enhancement. 100% local processing ensures complete privacy - no data transmission during optimization. Key Features: - Privacy-First: Complete local processing, no cloud dependencies - Cross-Platform: Native binaries for Windows, macOS (Intel/Apple Silicon), Linux (x64/ARM64) - Dual Optimization: Sophisticated rules engine + optional OpenAI LLM enhancement - Professional Tools: 50+ optimization techniques for technical and creative prompts - Template Management: Save, search, and reuse optimization patterns - Zero Setup: Works offline with cached license validation Perfect for developers, teams, and anyone requiring private prompt optimization without cloud dependencies.
Overview

Overview: (Summary section)

Privacy-first local prompt optimization with cross-platform native binaries. Features sophisticated AI-aware rules engine with optional OpenAI LLM enhancement. Perfect for users requiring complete data privacy and offline capability.

**Key Benefits:**
- Complete privacy with 100% local processing
- Works offline with cached validation
- Cross-platform native performance
- Dual optimization tiers (rules + optional LLM)
- Professional template management

Server Config

{
  "mcpServers": {
    "prompt-optimizer-local": {
      "command": "mcp-prompt-optimizer-local",
      "env": {
        "OPTIMIZER_API_KEY": "sk-local-pro-your-key-here",
        "OPENAI_API_KEY": "sk-proj-your-openai-key-here"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
nivlewd1
Star
-
Language
-
License
-
Category

Recommend Servers

View All
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