agentleFS
TehseenTechTehseenTech/manus-skills/skills/integration-skills/manus-mcp-configurator/SKILL.md

manus-mcp-configurator

Skill0 starsChanged 3 months agoMITView on GitHub

Automate Manus MCP server configuration. Use when adding, removing, listing, or validating MCP servers in Manus settings without manual JSON editing. Apply automatically when the request matches; the user does not need to mention this skill.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the task-specific instructions in this file before acting.

    line 15
  2. Distinctive:

    Use this skill when the request matches its description.

    line 21
  3. Distinctive:

    Add the two WADE MCP servers:

    line 29
  4. Very specific:

    Use remove_server.py to remove the existing server first

    line 135
  5. Very specific:

    Run validate_config.py to see specific errors

    line 139
  6. Distinctive:

    Check for missing commas, brackets, or quotes

    line 140
  7. Very specific:

    Validate after changes: Run validate_config.py after adding or removing servers

    line 145
  8. Distinctive:

    Backup configuration: Keep a backup before making changes

    line 148
  9. Distinctive:

    Test servers: Verify servers are running before adding them

    line 149

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Automate Manus MCP server configuration. Use when adding, removing, listing, or validating MCP servers in Manus settings without manual JSON editing. Apply automatically when the request matches; the user does not need to mention this skill.

This skill should apply automatically when the request matches; the user does not need to mention this skill.

Workflow

  1. Read the task-specific instructions in this file before acting.
  2. Apply the documented constraints, resources, and verification steps.
  3. Confirm the result against the requested outcome before completion.

Usage

Use this skill when the request matches its description. The skill is discovered automatically; the user does not need to mention the skill explicitly.

Manus MCP Configurator

Automate the management of MCP (Model Context Protocol) servers in your Manus configuration.

Quick Start

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"

Operations

Add a Server

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 description

Example:

python scripts/add_server.py \
  --name "my-custom-server" \
  --url "http://localhost:9000/mcp" \
  --description "My custom MCP server"

List All Servers

python scripts/list_servers.py [--json]

Options:

  • --json: Output as JSON instead of human-readable table

Example 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

Remove a Server

python scripts/remove_server.py --name <name>

Parameters:

  • --name: Name of the server to remove

Example:

python scripts/remove_server.py --name "wade-skillz"

Validate Configuration

python scripts/validate_config.py

Checks the configuration file for:

  • Valid JSON syntax
  • Required fields present
  • Proper data types
  • URL format correctness

Configuration File

The scripts automatically locate your Manus MCP configuration file by searching these locations in order:

  1. ~/.config/manus/mcp_config.json
  2. ~/.manus/mcp_config.json
  3. ~/Library/Application Support/Manus/mcp_config.json (macOS)
  4. $MANUS_CONFIG_PATH environment variable
  5. ./manus_mcp_config.json (fallback for testing)

For detailed format specification, see references/config-format.md.

Troubleshooting

"No Manus MCP configuration file found"

  • The configuration file doesn't exist yet
  • Set MANUS_CONFIG_PATH environment variable to the correct location
  • Or create a new file at ~/.config/manus/mcp_config.json

"Server already exists"

  • Use remove_server.py to remove the existing server first
  • Or choose a different server name

"Invalid JSON"

  • Run validate_config.py to see specific errors
  • Check for missing commas, brackets, or quotes
  • Restore from backup if available

Best Practices

  1. Validate after changes: Run validate_config.py after adding or removing servers
  2. Use descriptive names: Choose clear, unique names for servers
  3. Add descriptions: Include descriptions to document server purposes
  4. Backup configuration: Keep a backup before making changes
  5. Test servers: Verify servers are running before adding them

Examples

Add 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.