ProjectDocHelper

Created By
Stark1937a year ago
ProjectDocHelper is an MCP (Model Context Protocol) server designed to automatically generate project documentation and make it accessible to AI development tools like Cursor through MCP, thereby improving the accuracy and relevance of AI responses.
Overview

what is ProjectDocHelper?

ProjectDocHelper is an MCP (Model Context Protocol) server designed to automatically generate project documentation and make it accessible to AI development tools like Cursor, thereby improving the accuracy and relevance of AI responses.

how to use ProjectDocHelper?

To use ProjectDocHelper, install it via pip and run commands to generate documentation in either simple or detailed mode, and start the MCP server to allow AI tools to access the generated documents.

key features of ProjectDocHelper?

  • Smart Documentation Generation: Automatically generates document sets based on project type.
  • Multiple Generation Modes: Supports both simple and detailed modes for different needs.
  • Progress Visualization: Displays a progress bar during document generation.
  • MCP Service Support: Cursor can access generated documents after service startup.
  • Q&A Integration: Supports incorporating user-AI interactions into documentation.

use cases of ProjectDocHelper?

  1. Automatically generating documentation for frontend, backend, or full-stack projects.
  2. Enhancing AI-assisted development by providing relevant documentation to AI tools.
  3. Integrating user interactions into project documentation for better context.

FAQ from ProjectDocHelper?

  • Can ProjectDocHelper generate documentation for all project types?

Yes! It generates tailored documentation sets for frontend, backend, and full-stack projects.

  • Is ProjectDocHelper free to use?

Yes! ProjectDocHelper is open-source and free to use.

  • How does the Q&A integration work?

It intelligently identifies relevant Q&A content and adds it to the corresponding documents.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Stark1937
Star
0
Language
Python
License
-

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