Context Optimizer

Created By
malaksedarous10 months ago
Provides context optimization tools to extract targeted information rather than processing large files and command outputs in their entirety.
Overview

Context Optimizer MCP Server

A Model Context Protocol (MCP) server that provides context optimization tools for AI coding assistants including GitHub Copilot, Cursor AI, Claude Desktop, and other MCP-compatible assistants. It enables AI assistants to extract targeted information rather than processing large files and command outputs in their entirety.

Features

  • 🔍 File Analysis Tool (askAboutFile) - Extract specific information from files without loading entire contents
  • 🖥️ Terminal Execution Tool (runAndExtract) - Execute commands and extract relevant information using LLM analysis
  • ❓ Follow-up Questions Tool (askFollowUp) - Continue conversations about previous terminal executions
  • 🔬 Research Tools (researchTopic, deepResearch) - Conduct web research using Exa.ai's API
  • 🔒 Security Controls - Path validation, command filtering, and session management
  • 🔧 Multi-LLM Support - Works with Google Gemini, Claude (Anthropic), and OpenAI
  • ⚙️ Environment Variable Configuration - API key management through system environment variables
  • 🏗️ Simple Configuration - Environment variables only, no config files to manage
  • 🧪 Comprehensive Testing - Unit tests, integration tests, and security validation

Server Config

{
  "mcpServers": {
    "context-optimizer": {
      "command": "context-optimizer-mcp"
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
malaksedarous
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)

20 hours ago
Gpt Scrambler

2 days ago