skills/integration-skills/manus-mcp-configurator/SKILL.md
Automate Manus MCP server configuration. Use when adding, removing, listing, or validating MCP servers in Manus settings without manual JSON editing.
npx skillsauth add abcnuts/manus-skills manus-mcp-configuratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automate the management of MCP (Model Context Protocol) servers in your Manus configuration.
Add the two WADE MCP servers:
# Add wade-skillz server
python /home/ubuntu/skills/manus-mcp-configurator/scripts/add_server.py \
--name "wade-skillz" \
--url "http://127.0.0.1:8081/mcp" \
--description "WADE Skill Hub: Exposes all local skills as MCP tools"
# Add wade-skill-tester server
python /home/ubuntu/skills/manus-mcp-configurator/scripts/add_server.py \
--name "wade-skill-tester" \
--url "http://127.0.0.1:8082/mcp" \
--description "WADE Skill-Test-Runner: Automated skill testing tools"
python scripts/add_server.py --name <name> --url <url> [--description <desc>]
Parameters:
--name: Unique server identifier (e.g., "wade-skillz")--url: Full MCP endpoint URL (e.g., "http://127.0.0.1:8081/mcp")--description: Optional human-readable descriptionExample:
python scripts/add_server.py \
--name "my-custom-server" \
--url "http://localhost:9000/mcp" \
--description "My custom MCP server"
python scripts/list_servers.py [--json]
Options:
--json: Output as JSON instead of human-readable tableExample output:
📋 Configured MCP Servers (2 total):
================================================================================
1. wade-skillz
URL: http://127.0.0.1:8081/mcp
Description: WADE Skill Hub: Exposes all local skills as MCP tools
2. wade-skill-tester
URL: http://127.0.0.1:8082/mcp
Description: WADE Skill-Test-Runner: Automated skill testing tools
python scripts/remove_server.py --name <name>
Parameters:
--name: Name of the server to removeExample:
python scripts/remove_server.py --name "wade-skillz"
python scripts/validate_config.py
Checks the configuration file for:
The scripts automatically locate your Manus MCP configuration file by searching these locations in order:
~/.config/manus/mcp_config.json~/.manus/mcp_config.json~/Library/Application Support/Manus/mcp_config.json (macOS)$MANUS_CONFIG_PATH environment variable./manus_mcp_config.json (fallback for testing)For detailed format specification, see references/config-format.md.
"No Manus MCP configuration file found"
MANUS_CONFIG_PATH environment variable to the correct location~/.config/manus/mcp_config.json"Server already exists"
remove_server.py to remove the existing server first"Invalid JSON"
validate_config.py to see specific errorsvalidate_config.py after adding or removing serversAdd multiple servers at once:
# Add all WADE servers
for server in "wade-skillz:8081" "wade-skill-tester:8082" "wade-registry:8083"; do
IFS=':' read -r name port <<< "$server"
python scripts/add_server.py \
--name "$name" \
--url "http://127.0.0.1:$port/mcp" \
--description "WADE MCP Server: $name"
done
List and validate:
# Show current configuration
python scripts/list_servers.py
# Validate it
python scripts/validate_config.py
Clean up test servers:
# Remove all test servers
for name in "test-server-1" "test-server-2" "test-server-3"; do
python scripts/remove_server.py --name "$name"
done
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code