MCP Code Checker

Created By
MarcusJellinghausa year ago
MCP server providing code quality checks (pylint and pytest) with smart LLM-friendly prompts for analysis and fixes. Enables Claude and other AI assistants to analyze your code and suggest improvements.
Overview

What is MCP Code Checker?

MCP Code Checker is a Model Context Protocol (MCP) server that provides code quality checking operations, enabling AI assistants to perform quality checks on code within a specified project directory.

How to use MCP Code Checker?

To use MCP Code Checker, clone the repository, set up a virtual environment, install dependencies, and run the server with the command: python -m src.main --project-dir /path/to/project. You can also configure it to work with AI assistants like Claude.

Key features of MCP Code Checker?

  • Run pylint checks to identify code quality issues.
  • Execute pytest to identify failing tests.
  • Generate smart prompts for LLMs to explain issues and suggest fixes.
  • Combine multiple checks for comprehensive code quality analysis.

Use cases of MCP Code Checker?

  1. Identifying and fixing code quality issues in Python projects.
  2. Running automated tests to ensure code reliability.
  3. Enhancing debugging workflows by integrating AI assistance.

FAQ from MCP Code Checker?

  • Can MCP Code Checker be used with any Python project?

Yes! It can be used with any Python project by specifying the project directory.

  • Is there a graphical interface for MCP Code Checker?

No, it operates via command line and integrates with AI assistants for enhanced functionality.

  • What is the license for MCP Code Checker?

It is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MarcusJellinghaus
Star
0
Language
Python
License
MIT 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