Quack MCP Server

Overview

what is Quack MCP Server?

Quack MCP Server is a continuous integration server designed to automate code analysis and testing for Python code, providing tools for linting and static type analysis.

how to use Quack MCP Server?

To use Quack MCP Server, clone the repository, install the required dependencies, and start the server using the provided commands. You can also run it in a Docker container for easier deployment.

key features of Quack MCP Server?

  • Linting: Analyzes Python code for style and quality issues using pylint.
  • Static Analysis: Performs type checking using mypy to identify type errors.
  • Asynchronous Processing: Allows concurrent analysis of multiple code submissions.
  • Job Management: Track and retrieve results of submitted jobs.

use cases of Quack MCP Server?

  1. Automating code quality checks in CI/CD pipelines.
  2. Providing feedback on Python code submissions in educational settings.
  3. Integrating with development tools like Cline for real-time code analysis.

FAQ from Quack MCP Server?

  • Can Quack MCP Server analyze all Python code?

Yes! It supports various Python code analysis tasks including linting and static type checking.

  • Is Quack MCP Server free to use?

Yes! Quack MCP Server is open-source and free to use.

  • How can I run tests on Quack MCP Server?

You can run tests using pytest, with commands provided in the documentation.

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