mcp-auto-recovery
Skill0 starsChanged 3 months agoMITView on GitHub
Automatically diagnose and recover from MCP server connection issues. Use when any `manus-mcp-cli` command fails due to connection, authentication, or availability errors. Apply automatically when the request matches; the user does not need to mention this skill.
In this repository76 other files it gives its agents.
- app-store-submission-packagerSkill
- digital-product-inventorSkill
- ios-testflight-github-actionsSkill
- meta-ads-analyzerSkill
- get-to-know-a-clientSkill
- investigate-before-recommendSkill
- production-system-auditSkill
- similarweb-analyticsSkill
- stock-analysisSkill
- system-architectSkill
- autonomous-github-syncSkill
- autonomous-sync-scriptSkill
- github-gem-seekerSkill
- organize-github-reposSkill
- using-git-worktreesSkill
- brainstorm-logosSkill
- brand-driven-ux-overhaulSkill
- canvas-designSkill
- excel-generatorSkill
- frontend-designSkill
- inspirational-music-video-productionSkill
- theme-factorySkill
- video-generatorSkill
- multiplayer-game-builderSkill
- promo-code-systemSkill
- realistic-ai-persona-builderSkill
- role-based-access-controlSkill
- serverless-debuggingSkill
- vertical-expansion-blueprintSkill
- manus-mcp-configuratorSkill
- mcp-builderSkill
- mcp-connector-testerSkill
- mcp-ecosystem-optimizerSkill
- voice-ai-integrationSkill
- api-endpoint-builderSkill
- database-schema-generatorSkill
- testing-frameworkSkill
- deployment-automationSkill
- error-monitoring-setupSkill
- github-workflow-automationSkill
- analytics-dashboardSkill
- email-system-builderSkill
- feature-flag-systemSkill
- user-authentication-systemSkill
- cron-job-schedulerSkill
- file-upload-systemSkill
- notification-systemSkill
- payment-integrationSkill
- search-implementationSkill
- debug-mining-engineSkill
- doc-coauthoringSkill
- docxSkill
- internet-skill-finderSkill
- pdfSkill
- pptxSkill
- project-handoff-ingestionSkill
- serverless-debuggingSkill
- skill-arsenal-builderSkill
- skill-creatorSkill
- skill-demo-builderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Follow these steps sequentially.
- Very specific: line 60
After following the recommendation from the diagnostic report, retry the original manus-mcp-cli command that failed.
- Distinctive: line 64
If the issue persists, consult the reference file for common error messages and their solutions.
- Distinctive: line 96
Take action: Check spelling, verify MCP is enabled in session settings
- Distinctive: line 98
Retry: Run the original command again
- Distinctive: line 105
If all diagnostics pass but the command still fails, the issue is with the specific tool call parameters, not the MCP connection
≈ “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.
Files
Overview
Automatically diagnose and recover from MCP server connection issues. Use when any manus-mcp-cli command fails due to connection, authentication, or availability errors. 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.
MCP Auto-Recovery
This skill provides a systematic workflow to diagnose and resolve common issues when interacting with Model Context Protocol (MCP) servers via the manus-mcp-cli tool.
When to Use This Skill
Trigger this skill immediately if a manus-mcp-cli command fails with errors related to:
- Connection refused / timeout
- Server not found
- Authentication required / token expired
- Permission denied
- Any unexpected non-zero exit code
The Workflow
Follow these steps sequentially. Do not skip steps.
Step 1: Identify the Failing Server
From the failed command, identify the server name specified with the --server flag. For example, in manus-mcp-cli tool list --server supabase, the server name is supabase.
Step 2: Run the Diagnostic Script
Execute the bundled diagnostic script, passing the server name as an argument. This script will perform a series of automated checks and provide a summary report with recommended actions.
Command:
python3 /home/ubuntu/skills/mcp-auto-recovery/scripts/diagnose_mcp.py <server_name>Example:
python3 /home/ubuntu/skills/mcp-auto-recovery/scripts/diagnose_mcp.py supabaseStep 3: Interpret the Diagnostic Report
The script will output a clear summary. Follow its recommendation:
| Report Outcome | Recommended Action |
| Server Not Available | Check the server name for typos against the list of available servers provided. Retry the command with the correct name. |
| Authentication Failed | Follow the interactive OAuth prompts if they appear. The script cannot do this for you. After authenticating, retry the original command. |
| All Checks Pass | The issue is not with the connection. The problem lies with the specific tool call itself. Carefully review the tool's required parameters, your input JSON, and any necessary permissions (e.g., does the user have access to the requested resource?). |
Step 4: Retry the Original Command
After following the recommendation from the diagnostic report, retry the original manus-mcp-cli command that failed. If it still fails, do not run the diagnostic script again. Instead, inform the user about the persistent failure and the steps you've already taken.
Advanced: Common Error Patterns
If the issue persists, consult the reference file for common error messages and their solutions.
Command:
cat /home/ubuntu/skills/mcp-auto-recovery/references/common_errors.mdExample Usage
Scenario: Supabase Connection Fails
Failed Command:
manus-mcp-cli tool call execute_sql --server supabase --input '{"query": "SELECT * FROM users"}'Error:
Error: failed to get server config: server 'supabase' not foundRecovery Steps:
- Identify server:
supabase - Run diagnostic:
python3 /home/ubuntu/skills/mcp-auto-recovery/scripts/diagnose_mcp.py supabase- Read report: Script shows server is not available and lists all configured servers
- Take action: Check spelling, verify MCP is enabled in session settings
- Retry: Run the original command again
Notes
- The diagnostic script is non-destructive and safe to run multiple times
- It only performs read operations to check server status
- Authentication flows must be completed interactively by the user
- If all diagnostics pass but the command still fails, the issue is with the specific tool call parameters, not the MCP connection
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
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.