Aindreyway MCP Codex Keeper

Created By
aindreywaya year ago
An intelligent MCP server that serves as a guardian of development knowledge, providing Cline assistants with curated access to latest documentation and best practices across the software development landscape
Overview

What is Aindreyway MCP Codex Keeper?

Aindreyway MCP Codex Keeper is an intelligent MCP server designed to serve as a guardian of development knowledge, providing Cline assistants with curated access to the latest documentation and best practices across the software development landscape.

How to use Aindreyway MCP Codex Keeper?

To use the MCP Codex Keeper, ensure Node.js is installed (version 18 or higher), then configure it by adding specific settings to your Cline/Sonnet configuration and executing it using npx.

Key features of Aindreyway MCP Codex Keeper?

  • Automatically manages documentation from various sources
  • Intelligent search capabilities for documentation
  • Supports tagging and categorization of documentation
  • Updates documentation automatically to keep it current
  • Optimizes memory usage for better performance

Use cases of Aindreyway MCP Codex Keeper?

  1. Retrieving the latest documentation for React.
  2. Finding best practices for TypeScript development.
  3. Searching for information about asynchronous programming techniques.

FAQ from Aindreyway MCP Codex Keeper?

  • How can I access the latest documentation?

    You can ask your assistant to "Show me the latest React documentation" to retrieve it instantly.

  • What types of documentation can be added?

    Documentation sources can include topics from frontend, backend, database, DevOps, and more.

  • Is there a support channel for this project?

    Yes, you can refer to the Contributing Guide for more information on support.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aindreyway
Star
-
Language
-
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