mcp-server-management

Configure MCP tool servers in HiClaw with YAML templates and mcporter verification.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill mcp-server-management-agentscope-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcp-server-management
Source: https://github.com/agentscope-ai/HiClaw/tree/main/manager/agent/skills/mcp-server-management
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill mcp-server-management-agentscope-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps administrators configure MCP tool servers for HiClaw by turning a user request (new integration, credential rotation, or access changes) into a correctly provisioned and auditable gateway setup.

Core Features & Use Cases

  • Create/update MCP tool servers from REST API templates: Deploy a server using built-in templates (e.g., GitHub) or a user-provided YAML definition.
  • Proxy existing MCP servers (SSE/HTTP): Connect external MCP backends through the Higress AI Gateway using transport-aware proxy configuration.
  • Rotate credentials and control worker access: Update stored credentials, configure consumer authorization, and ensure only relevant workers are notified.
  • Operational verification workflow: Enforces waiting for auth plugin activation and end-to-end connectivity checks via mcporter before making tools available.

Quick Start

Use the mcp-server-management skill to set up or rotate credentials for an MCP tool server using the provided server name and credential, then verify it end-to-end before notifying workers.

Frequently Asked Questions about mcp-server-management

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

FAQPage Schema
How do I configure an MCP tool server using a REST API YAML template?▼

To configure an MCP tool server, you apply a built-in or user-provided YAML template by substituting your credentials via the accessToken: "" key. This provisions the gateway-facing server definition for your REST-to-MCP integration.

Can I proxy external MCP backends over SSE or StreamableHTTP?▼

Yes, you can proxy existing MCP servers by configuring transport-aware proxy settings through the Higress AI Gateway. This connects external MCP backends over SSE or StreamableHTTP without requiring direct local hosting.

What is the best way to rotate credentials for an MCP server with controlled worker access?▼

Rotating MCP server credentials involves updating stored credentials, configuring consumer authorization, and distributing updated mcporter configurations. This ensures only relevant workers are notified and authorized after the change.

Does MCP server management require local deployment mode?▼

Yes, MCP server management requires local deployment mode. The system does not support aliyun script execution, meaning you must operate within a local environment to provision gateway definitions and activate auth plugins.

Why does my MCP server onboarding fail before worker notification?▼

MCP server onboarding fails if you skip the operational verification workflow. You must wait for auth plugin activation and perform end-to-end connectivity checks via mcporter before making tools available to workers.

When do I need to configure consumer authorization for a gateway-facing MCP server?▼

You need to configure consumer authorization whenever you update gateway-facing server definitions or rotate credentials. This ensures workers receive valid mcporter configurations and are explicitly authorized to access the proxied tools.