mcp-tooling-layer

Validate MCP server connectivity and classify stack status before orchestration.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill mcp-tooling-layer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-tooling-layer
Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/mcp-tooling-layer
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill mcp-tooling-layer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, jq, node, playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Prevents orphaned orchestration work by validating and cataloging every MCP connection before domain skills access live infrastructure, eliminating blind code generation against mismatched schemas or downed services.

Core Features & Use Cases

  • Connectivity auditing: Runs the MCP health check script to verify supabase, postgres, filesystem, playwright, and Google Maps MCP statuses and classify the stack as FULL, PARTIAL, or OFFLINE.
  • Configuration guidance: Documents config file locations, JSON templates, environment variable requirements, and troubleshooting steps so setup errors are resolved before tasks execute.
  • Degraded mode protocols: Supplies fallback behaviors for each MCP server so migrations, QA gates, and UI checks continue with clear status reports even when live tools are unavailable.

Quick Start

Run the included health check before orchestrating domain skills to confirm every MCP server is reachable.

Frequently Asked Questions about mcp-tooling-layer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check MCP server connectivity before running orchestration tasks?

To verify MCP server connectivity, run a health check script that tests supabase, postgres, filesystem, playwright, and Google Maps MCP statuses, classifying the stack as FULL, PARTIAL, or OFFLINE.

Why does my Claude orchestration workflow generate code against mismatched schemas?

Orchestration workflows generate mismatched code when MCP connections are down or unverified. Validating and cataloging every MCP server connection before domain skills access live infrastructure prevents this blind code generation.

What environment variables do I need to configure for supabase and postgres MCP servers?

Configuring supabase and postgres MCP servers requires environment variables including SUPABASE_ACCESS_TOKEN, POSTGRES_URL, and GOOGLE_MAPS_API_KEY, alongside JSON configuration entries for each server.

Can I continue QA gates and UI checks when playwright or supabase MCP is offline?

Yes, you can continue QA gates and UI checks when MCPs are offline by using degraded mode protocols. These supply fallback behaviors so migrations and visual validations proceed with clear status reports.

Does MCP connectivity auditing require Docker and Node.js to run health checks?

Yes, MCP connectivity auditing requires Docker and Node.js as dependencies to execute the health verification scripts and support the playwright MCP environment for visual validation tasks.