Skippr Extension MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skippr_list_issuesB | Lists all available Skippr issues with optional filtering by project, review, severity, category, and resolution status |
| skippr_get_issueA | Gets full details for a specific Skippr issue including raw markdown content |
| skippr_list_projectsA | Lists all available project IDs from the .skippr/projects directory |
| skippr_restart_extension_serverB | Restarts the WebSocket server that communicates with browser extensions |
| skippr_extension_server_statusB | Gets the current status of the WebSocket server for browser extensions |
| skippr_send_to_extensionB | Sends a message to a specific browser extension by its ID |
| skippr_notify_project_extensionsB | Sends a message to all browser extensions connected to a specific project |
| skippr_notify_all_extensionsA | Broadcasts a message to all connected browser extensions |
| skippr_list_connected_extensionsB | Lists all currently connected browser extensions |
| skippr_disconnect_extensionB | Disconnects a specific browser extension by its ID |
| skippr_verify_issue_fixB | Requests verification from the browser extension to check if an issue has been fixed |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: extension server management, issue/project listing, and issue verification. No two tools overlap in functionality.
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.
11 tools is reasonable for a server that handles both extension communication and issue management. Slightly on the higher side but well-organized.
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.