mcp-server
Guide for integrating and managing custom Model Context Protocol (MCP) servers within the Cursor IDE environment.
Discover reusable agent skills, browse implementation details, and find the right skill for your workflow.
551 skills found
Guide for integrating and managing custom Model Context Protocol (MCP) servers within the Cursor IDE environment.
Controls a local or remote headless browser for automated web navigation, data extraction, form interaction, and testing from sandboxed environments.
Sends debugging data, logs, and visual output to the Ray desktop application via its local API for real-time developer feedback.
A specialized code review agent that performs multi-dimensional analysis covering security vulnerabilities, performance optimization, code quality, and maintainability standards.
Expert CLI guides for AI agents, featuring senior engineer workflows, safety guardrails, and operational patterns for cloud, IaC, containers, databases, and dev tools.
Manage, deploy, and debug GitHub MCP servers and gateways. Orchestrate Docker-based MCP containers, troubleshoot connectivity, handle authentication, and integrate with Copilot CLI and Agentic Workflow Firewalls.
Designer's eye QA: detects and automates fixes for visual inconsistencies, spacing, hierarchy, and UI polish issues. Iteratively verifies with before/after screenshots.
Advanced exploratory testing with SBTM, RST heuristics, and test tours. Use for investigating bugs, discovering unknown risks, and structured manual exploration.
Emergency recovery suite for Vercel-hosted projects. Manage deployment rollbacks, database migration reverts, cache invalidation, and health verification workflows.
Automated toolkit for creating, maintaining, and enhancing CLAUDE.md files to ensure your project's AI-assisted development guidelines are always accurate, modular, and best-practice compliant.
Automated Python virtual environment manager for project isolation, dependency management, and lifecycle validation.
Apply context-driven testing principles to adapt testing strategies based on project goals, risks, and constraints rather than relying on universal best practices.