lawzava/megapowers / extras/skills/mcp-setup
mcp-setup
VerifiedUse when installing, configuring, debugging, or verifying an MCP server for a harness, or when a configured server's tools are missing or failing.
MCP Setup
Resolve the exact scope first: which harness, which configuration file, and whether the server is global, project, or repository-local. Keep one registration channel per server; duplicate registrations across scopes produce conflicting tool lists and ambiguous failures.
Servers register at session start. Some harnesses reconnect a server or refresh its tools live; after a configuration change, reconnect the server from the harness's server menu when it offers one, otherwise restart the session. A tool missing from a live session is not evidence of a broken server.
Treat diagnostic output as secret-bearing. A harness's server-list command and configuration dumps can print arguments, headers, and connection strings verbatim; filter values out before the output reaches the transcript. Start with a read-only status check of the configured servers before any login attempt. Match the authentication flow to the execution mode. Browser OAuth needs an interactive terminal, not a local browser: on a remote or display-less host, a login command that prints the authorization URL and accepts the pasted callback URL completes the grant. A non-interactive session cannot finish it. Provision a token, complete the grant interactively beforehand, or route through a proxy command that owns its own authentication. Record where the credential lives, and never write it into configuration committed to a repository.
Attempt re-authentication at most once per server. If it fails, stop: report the exact error text and the user action needed (complete the browser grant, issue a token with the missing scope, or fix the registration). Do not retry, probe other login commands, or substitute a CLI for the server unless asked. When a server needs login again the same day, find why before asking: a provider with short-lived tokens and rejected refresh keeps expiring. Propose a durable token or header setup; ask to reconnect once per root cause.
Verify with a fresh probe, not the current session: start a new non-interactive session, list the server's tools, and call one read-only tool. Redact tokens and account identifiers before quoting probe output. A sandboxed probe can report a healthy server as broken when the sandbox blocks its state or socket files; re-run the probe outside the sandbox before concluding failure.
On failure, report the harness, scope, configuration path, server name,
transport, authentication mode, exit status, and raw error. Use
systematic-debugging to distinguish launcher, authentication, quota, and
provider failures. Do not edit credentials you cannot verify.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |