Troubleshooting Config Errors

This usually indicates a JSON syntax error in your config file. Use a JSON validator like jsonlint.com to check your config. Common issues: missing commas, trailing commas, or unmatched braces. The Config Generator prevents these errors.

First, verify the config file was saved. Then, completely quit and restart Claude Desktop (not just the chat window). Check Claude's console logs for error messages during startup—missing environment variables or failed connections will be logged there.

If Claude shows 'authentication failed' errors, verify your API keys or tokens. For GitHub and GitLab, ensure tokens have the correct scopes (repo, read_user, etc.). For OAuth-based services like Google Drive, tokens may need to be refreshed.

Filesystem skill errors often relate to path permissions. On macOS, you may need to grant Claude Desktop Full Disk Access in System Preferences > Privacy & Security. On Linux, ensure the specified paths are readable by your user.

API-based skills may fail if your network requires a proxy. Check if the MCP server supports HTTP_PROXY environment variables. For self-hosted services, verify they're accessible from your machine and not blocked by firewalls.

If you're still stuck, check the skill's verification status on AgentStack. Verified skills have been tested and confirmed working. You can also search for error messages in the Claude community forums or the skill's GitHub repository.