comment-stripper-mcp

Created By
yhziona year ago
A flexible MCP server that batch processes code files to remove comments across multiple programming languages. Currently supports JavaScript, TypeScript, and Vue files with regex-based pattern matching. Handles individual files, directories (including subdirectories), and text input. Built for clean code maintenance and preparation.
Overview

what is comment-stripper-mcp?

comment-stripper-mcp is a flexible MCP server designed to batch process code files and remove comments across multiple programming languages, including JavaScript, TypeScript, Vue, CSS/SCSS/LESS, HTML, Python, Java, C#, C++, Ruby, and PHP.

how to use comment-stripper-mcp?

To use comment-stripper-mcp, clone the repository, install the dependencies, and run the server in development or production mode. You can send requests to the API to strip comments from files or directories.

key features of comment-stripper-mcp?

  • Batch processing of individual files, directories, or raw text input
  • Cross-language support for various programming languages
  • Recursive handling of nested directories
  • Regex-based pattern matching for efficient comment removal
  • MCP-compliant API for easy integration
  • Comprehensive logging and error handling
  • Performance optimization for large files

use cases of comment-stripper-mcp?

  1. Cleaning up code before deployment by removing unnecessary comments.
  2. Preparing code for open-source contributions by stripping out comments.
  3. Automating the comment removal process in CI/CD pipelines.

FAQ from comment-stripper-mcp?

  • What programming languages does comment-stripper-mcp support?

It supports JavaScript, TypeScript, Vue, CSS/SCSS/LESS, HTML, Python, Java, C#, C++, Ruby, and PHP.

  • How do I run the server?

You can run the server in development mode using npm run dev or in production mode using npm start after building the project.

  • Is there an API for this project?

Yes, comment-stripper-mcp provides an API to strip comments from code files and check processing progress.

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

2 days ago