Manage Recce MCP server tool handlers and error classification.
npx skills add https://github.com/DataRecce/recce --skill recce-mcp-dev
Please help me install this Agent Skill. Skill: recce-mcp-dev Source: https://github.com/DataRecce/recce/tree/main/.claude/skills/recce-mcp-dev Command: npx skills add https://github.com/DataRecce/recce --skill recce-mcp-dev
Provides focused guidance and testing patterns for modifying the Recce MCP server, its tool handlers, error classification, and MCP-related tests so changes behave correctly and consistently across environments.
Run the local unit and integration test suites, confirm new or changed tool handlers follow the response contract and error classification rules, and then invoke the E2E gate by running /recce-mcp-e2e when ready.
High-intent search queries and answers about installing and using this skill.
To add an MCP server tool handler, implement the handler to raise errors for SDK isError semantics rather than returning them. Include additive metadata only in the response payload to maintain protocol consistency.
MCP tool errors should be classified using a prioritized system that consistently handles permission, missing table, and syntax errors. This ensures predictable behavior across different tool handlers and environments.
MCP server tool handlers require a three-layer testing strategy: unit tests for handler logic, integration tests for MCP protocol integration, and smoke tests with E2E verification for real-world tool behavior across local CI and manual checks.
MCP server tool response format breaks SDK error handling when handlers return errors instead of raising them for isError semantics. Handlers must raise errors directly and only include additive metadata in successful responses.
Modifying recce/mcp_server.py tool handlers requires updating associated unit, integration, and smoke tests. Changes must pass the three-layer test coverage and E2E verification gate to ensure consistent behavior.
The best way to verify MCP server changes is to run local unit and integration test suites, confirm tool handlers follow error classification rules and response contracts, then invoke the E2E gate for final verification.
diegosouzapwPackage upstream Recce MCP development workflows with provenance and bundled guidance.
soniqoRun Swift unit or end-to-end test suites against a local codebase.
mvillmowGenerate HTML and terminal coverage reports for Python pytest runs.
cyanheadsAutomate MCP tool and resource handler tests with Vitest and mock contexts.
