MCP.so
Sign In

Local Scanner MCP Server

@treaties-ai

About Local Scanner MCP Server

MCP server for scanning local code and localhost URLs

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

treaties-ai

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "local-scanner-mcp": {
      "url": "http://localhost:3000",
      "waitTime": 2000,
      "actions": [
        {
          "type": "click",
          "selector": "#login-button"
        },
        {
          "type": "type",
          "selector": "#username",
          "text": "testuser"
        },
        {
          "type": "type",
          "selector": "#password",
          "text": "password"
        },
        {
          "type": "click",
          "selector": "#submit-button"
        },
        {
          "type": "wait",
          "time": 1000
        }
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Local Scanner MCP Server?

Local Scanner MCP Server is a Model Context Protocol (MCP) server that enables AI assistants to scan local code and localhost URLs. It provides tools for validating code style, capturing screenshots of local web pages, analyzing console logs, and checking HTML compliance. It is designed for developers using AI assistants like Cline (VSCode) or Cascade (WindSurf) to interact with local development environments.

How to use Local Scanner MCP Server?

Install dependencies with npm install, build with npm run build, and start with npm start. Then configure an MCP client (e.g., for Cline or WindSurf) by editing the respective settings file and providing the path to the built server (build/index.js). The server exposes four tools: scan_localhost, screenshot_localhost, lint_code, and validate_html.

Key features of Local Scanner MCP Server

  • Access and scan localhost URLs for runtime errors
  • Capture full-page or partial screenshots of local web pages
  • Lint JavaScript, TypeScript, and CSS files
  • Validate HTML content or URLs for standards compliance
  • Perform automated page interactions (click, type, wait)
  • Integrates seamlessly with MCP AI assistant clients

Use cases of Local Scanner MCP Server

  • Debugging locally running web applications with an AI assistant
  • Visually verifying frontend changes via screenshots
  • Enforcing code quality by linting files during development
  • Ensuring web pages meet HTML accessibility standards

FAQ from Local Scanner MCP Server

What are the runtime requirements?

Node.js and npm are required. The server is built and run using Node.js.

How do I configure this server with Cline or WindSurf?

Edit the MCP settings file: for Cline, ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json; for WindSurf, ~/Library/Application Support/WindSurf/windsurf_config.json. Add an entry with command "node" and args pointing to build/index.js.

What URLs can be scanned or screenshotted?

Only URLs starting with http://localhost or https://localhost are allowed.

What file types can be linted?

JavaScript, TypeScript, and CSS files. Language can be auto-detected from file extension or specified manually.

Does the server support automated interactions on web pages?

Yes, scan_localhost accepts an optional actions list for clicking, typing, and waiting.

Comments

More Other MCP servers