openclaw-hq-mcp-gateway-tools

Route agent tasks to correct MCP gateway backends with safety guardrails.

Updated May 7, 2026
One-click install
npx skills add https://github.com/MOODMNKY-LLC/mnky-atlas --skill openclaw-hq-mcp-gateway-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-hq-mcp-gateway-tools
Source: https://github.com/MOODMNKY-LLC/mnky-atlas/tree/main/skills/openclaw-hq-mcp-gateway-tools
Command: npx skills add https://github.com/MOODMNKY-LLC/mnky-atlas --skill openclaw-hq-mcp-gateway-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of failed operations, wasted API calls, and unsafe data access caused by incorrect tool routing when using the unified MOOD MNKY HQ MCP gateway, which requires matching tasks to the correct backend for reliable, secure execution.

Core Features & Use Cases

  • Intelligent Backend Selection: Provides a clear matrix to match tasks to the correct backend (filesystem, fetch, github, brave-search, git, postgres, memory, sequential-thinking) to avoid unsafe or wasteful routing.
  • Safe Operation Guardrails: Enforces best practices such as sequencing reads before writes, retrying only idempotent write operations, and never exposing bearer tokens in user-facing artifacts.
  • Pre-built Workflow Templates: Offers ready-made, step-by-step workflows for common engineering tasks including incident triage, repository fixes with pull requests, and deep research alignment.
  • Failure Recovery Guidance: Includes a troubleshooting table to resolve common issues like missing tools, filesystem access denials, and git push rejections.

Quick Start

Use the openclaw-hq-mcp-gateway-tools skill to investigate the recent production outage by following the incident triage workflow and selecting the appropriate backends for each investigation step.

Frequently Asked Questions about openclaw-hq-mcp-gateway-tools

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

FAQPage Schema
How do I select the correct MCP backend for agent workflows?

Selecting the correct MCP backend requires matching your task to the appropriate gateway backend, such as filesystem, fetch, github, brave-search, git, postgres, memory, or sequential-thinking, to ensure safe and efficient operation execution.

What are the safe operation guardrails for MCP gateway tool routing?

Safe operation guardrails for MCP gateway tool routing include enforcing read-before-write sequencing, retrying only idempotent write operations, protecting bearer tokens from user-facing exposure, and applying backend-specific access controls to prevent unsafe data access.

How do I run an incident triage workflow using an MCP gateway?

Running an incident triage workflow using an MCP gateway involves following pre-built, step-by-step templates that guide you through selecting the appropriate backends for each investigation step to diagnose and resolve production outages efficiently.

Why does MCP gateway tool routing fail and how do I fix it?

MCP gateway tool routing fails due to missing tools, filesystem access denials, or git push rejections; you can fix it by consulting a troubleshooting table that provides failure recovery guidance to resolve these common routing issues.

Can I use sequential-thinking and postgres backends together for multi-step reasoning?

Yes, you can use sequential-thinking and postgres backends together for multi-step reasoning tasks by routing your operations through the unified MCP gateway, which supports matching complex multi-step workflows to the correct backend.