Rector Mcp

Created By
vasilvestre7 months ago
Overview

what is Rector Mcp?

Rector Mcp is a server that provides tools to query and filter Rector PHP refactoring rules, enabling developers to automate and streamline their code refactoring processes.

how to use Rector Mcp?

To use Rector Mcp, you can run the server directly from GitHub Packages using the command npx @vasilvestre/mcp-rector. For a permanent installation, you can install it globally with npm install -g @vasilvestre/mcp-rector.

key features of Rector Mcp?

  • Query and filter Rector rules easily.
  • Supports multiple installation methods (quick start, global installation, development setup).
  • Integration with various development environments like Claude Desktop, Cline, and Zed Editor.

use cases of Rector Mcp?

  1. Automating PHP code refactoring tasks.
  2. Integrating with IDEs for seamless development experience.
  3. Testing and verifying refactoring rules locally before deployment.

FAQ from Rector Mcp?

  • Can I run Rector Mcp without installation?

Yes! You can run it directly using npx without any installation.

  • How do I configure it with my IDE?

You can add the configuration to your IDE's settings as specified in the documentation for each supported IDE.

  • What if I encounter permission issues?

Ensure you have Node.js 18+ installed and check your permissions or try using npx --yes mcp-rector.

Server Config

{
  "mcpServers": {
    "rector": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-rector"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
vasilvestre
Star
-
Language
-
License
-
Tags

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