Skip to main content
Glama
Skippr Extension MCP Server

Skippr Extension MCP Server

by skippr-hq

Skippr Extension MCP Server

Website NPM Version MIT licensed

Skippr Extension MCP Server acts as a bridge between product issues identified by Skippr's browser extension. Built upon MCP, it enables your coding agent to discover, understand, and fix issues such as UX inconsistencies, accessibility violations, and product quality problems seamlessly.

Key Features

  • Natural language interaction: Fix product issues using intuitive, conversational commands with your AI coding agent.

  • Seamless integration: Works with Claude Code, Cursor, Copilot, and other MCP-compatible coding assistants.

  • Real-time issue sync: Automatically receives issues from Skippr's browser extension as you review your product.

  • AI-powered reviews: Get insights from specialized AI agents that review your product like a PM, designer, content strategist, and accessibility expert would.

  • Context-rich details: Each issue includes actionable prompts, element metadata, and suggested fixes.

  • Project-based organization: Manage multiple projects with isolated issue tracking.

Related MCP server: autonomous-frontend-browser-tools

Prerequisites

Before setting up the Skippr MCP server, ensure you have:

  • An MCP Coding Agent Client application (Claude Code, Cursor, VS Code, etc.)

  • Node.js >= v22.x

  • Skippr Chrome Extension installed and configured

Installation

Run this command in your terminal. See Claude Code MCP docs for more info.

Claude Code Local Server Connection

claude mcp add skippr-extension-mcp -- npx -y @skippr/extension-mcp-server

After installation, the Skippr Extension MCP server will be available in your Claude Code sessions. You can start using natural language commands to interact with your product issues.

Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server

Paste the following configuration into your Cursor ~/.cursor/mcp.json file. You may also install in a specific project by creating .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.

Cursor Local Server Connection

{
  "mcpServers": {
    "skippr-extension-mcp": {
      "command": "npx",
      "args": ["-y", "@skippr/extension-mcp-server"]
    }
  }
}

After adding the configuration, restart Cursor to activate the MCP server.

Add the following to your VS Code settings.json file (accessible via Command Palette > Preferences: Open User Settings (JSON)). See VS Code MCP docs for more info.

"mcp": {
  "servers": {
    "skippr-extension-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@skippr/extension-mcp-server"]
    }
  }
}

After adding the configuration, reload VS Code to activate the MCP server.

Usage Examples

Once installed, interact with Skippr using natural language commands in your coding assistant:

  • Show me all high-severity accessibility issues in my project

  • List all unresolved UX issues for the latest review

  • Get details for issue abc-123 and help me fix it

  • What product issues do I have across all my projects?

Support

For questions, technical support, or feedback:

© 2025 Skippr - Released under MIT License

Available Tools

11 tools
skippr_disconnect_extensionDisconnect ExtensionB

Disconnects a specific browser extension by its ID

Inputs: extensionId (required). Returns: success, extensionId, message

skippr_extension_server_statusExtension Server StatusB

Gets the current status of the WebSocket server for browser extensions

Inputs: no named parameters. Returns: running, port

skippr_get_issueGet Skippr Issue DetailsA

Gets full details for a specific Skippr issue including raw markdown content

Inputs: projectId (required), reviewId (required), issueId (required). Returns: id, reviewId, title, severity, +3 more

skippr_list_connected_extensionsList Connected ExtensionsB

Lists all currently connected browser extensions

Inputs: no named parameters. Returns: totalExtensions, extensions

skippr_list_issuesList Skippr IssuesB

Lists all available Skippr issues with optional filtering by project, review, severity, category, and resolution status

Inputs: projectId (required), reviewId, severity, category, +1 more. Returns: issues, totalCount

skippr_list_projectsList Skippr ProjectsA

Lists all available project IDs from the .skippr/projects directory

Inputs: no named parameters. Returns: projects, totalCount

skippr_notify_all_extensionsNotify All ExtensionsA

Broadcasts a message to all connected browser extensions

Inputs: type (required), payload. Returns: sent, failed, message

skippr_notify_project_extensionsNotify Project ExtensionsB

Sends a message to all browser extensions connected to a specific project

Inputs: projectId (required), type (required), payload. Returns: projectId, sent, failed, message

skippr_restart_extension_serverRestart Extension ServerB

Restarts the WebSocket server that communicates with browser extensions

Inputs: port. Returns: success, message, port

skippr_send_to_extensionSend Message to ExtensionB

Sends a message to a specific browser extension by its ID

Inputs: extensionId (required), type (required), payload. Returns: success, extensionId, message

skippr_verify_issue_fixVerify Issue FixB

Requests verification from the browser extension to check if an issue has been fixed

Inputs: projectId (required), issueId (required), reviewId (required), timeout. Returns: success, projectId, issueId, verified, +4 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: extension server management, issue/project listing, and issue verification. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent 'skippr_verb_noun' pattern with clear action and target (e.g., skippr_list_issues, skippr_disconnect_extension). No mixing of styles.

    Tool Count4/5

    11 tools is reasonable for a server that handles both extension communication and issue management. Slightly on the higher side but well-organized.

    Completeness3/5

    Covers extension lifecycle well (connect, disconnect, list, notify, restart) and provides issue listing and verification, but lacks issue creation, update, or deletion, leaving workflow gaps.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      Unleashes LLM-powered agents to autonomously execute and debug web apps directly in your code editor, with features like webapp navigation, network traffic capture, and console error collection.
      2
      1,232
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to debug frontend applications by providing direct access to browser DevTools, React state, DOM inspection, and runtime debugging capabilities. Bridges the gap between AI and complex web applications for autonomous debugging and issue resolution.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Bridges AI coding agents with the browser to provide visual debugging, real-time error capture, screenshot capabilities, DOM inspection, and interactive wireframing through a reverse proxy with injected developer tools.
      47 npm
      22
      Apache 2.0