Knip Mcp Server

Created By
gtriasa year ago
This MCP server provides AI agents with powerful code cleanup capabilities through knip.dev integration. It's designed to work seamlessly with Cursor AI and other MCP-compatible tools to maintain clean, efficient codebases.
Overview

What is Knip MCP Server?

Knip MCP Server is a Model Control Protocol (MCP) server that integrates with knip.dev to assist AI agents in identifying and cleaning up unused files, imports, exports, and dependencies in JavaScript/TypeScript projects.

How to use Knip MCP Server?

To use Knip MCP Server, install it via npm and run the server directly or through npx. Configure it using environment variables to set project paths and logging levels.

Key features of Knip MCP Server?

  • Comprehensive code analysis to find unused code
  • Detection of unused files and imports/exports
  • Management of unused npm dependencies
  • Built-in safety checks and backup mechanisms
  • Full support for monorepo and workspace setups
  • Dry run mode to preview changes before applying them

Use cases of Knip MCP Server?

  1. Cleaning up code after feature implementation
  2. Auditing dependencies for unused packages
  3. Conducting health checks on codebases

FAQ from Knip MCP Server?

  • Can Knip MCP Server clean up all types of projects?

Yes! It is designed for JavaScript and TypeScript projects.

  • Is Knip MCP Server free to use?

Yes! It is open-source and free for everyone.

  • How does the dry run mode work?

The dry run mode allows you to preview changes without making any modifications, ensuring safety during cleanup operations.

Server Config

{
  "mcpServers": {
    "knip": {
      "command": "npx",
      "args": [
        "@genar/knip-mcp-server"
      ],
      "env": {
        "KNIP_PROJECT_ROOT": ".",
        "KNIP_LOG_LEVEL": "info",
        "KNIP_SAFE_MODE": "true"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gtrias
Star
-
Language
-
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