Mcp Phpcs Server

Created By
larspohlmann7 months ago
Overview

what is MCP PHPCS Server?

MCP PHPCS Server is a minimal Model Context Protocol (MCP) server implemented in pure PHP that provides tools for PHP code quality checking and fixing.

how to use MCP PHPCS Server?

To use the MCP PHPCS Server, you need to mark the script as executable and configure your MCP client to start the server via stdio using the provided command.

key features of MCP PHPCS Server?

  • Runs PHP_CodeSniffer to check code quality and returns a readable report.
  • Runs PHP Code Beautifier and Fixer to automatically fix code style issues.
  • No Composer dependencies, making it easy to integrate into any project.

use cases of MCP PHPCS Server?

  1. Ensuring code quality in PHP projects by checking for coding standard violations.
  2. Automatically fixing code style issues to maintain consistency across codebases.
  3. Integrating with development environments to provide real-time feedback on code quality.

FAQ from MCP PHPCS Server?

  • Does MCP PHPCS Server require any dependencies?

No, it is designed to have no Composer dependencies and can be copied into any project.

  • How do I configure the MCP PHPCS Server?

You can configure it via environment variables or a configuration file.

  • What output format does the server provide?

The server outputs JSON-RPC messages to STDOUT and logs to STDERR.

Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
larspohlmann
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)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago