Connection Issues
Server fails to start or connect
-
Use absolute paths: Specify the full path to your server
- ✅ Good:
/Users/yourname/project/server.py - ❌ Bad:
./server.pyorserver.py
- ✅ Good:
-
For
uvprojects: Use the--directoryflag with absolute path - Test your command first: Run the server command manually in a terminal to verify it works before adding it to Inspector
-
For HTTP servers: Verify the URL is accessible
- Test with
curlor a browser first
- Test with
Authentication Issues
Server fails to connect with authentication errors
If your server is failing to connect, first verify you’ve selected the correct authentication option:- No Authentication - Use this for local or development servers that don’t require authentication
- Bearer Token - Use this if you already have an API token from the server
- OAuth 2.0 - Use this for servers that require OAuth authorization flow
Getting 401 Unauthorized errors
If you’re seeing 401 Unauthorized errors when trying to connect to your server, this typically means the server requires authentication that hasn’t been set up yet. Solution:- Change your authentication type to OAuth 2.0 in the server configuration
- Go through the OAuth authorization flow to obtain credentials
- Use the OAuth Debugger to troubleshoot any issues with the OAuth process
The OAuth Debugger helps you step through each part of the authorization
process and identify where things might be going wrong.
Common Configuration Mistakes
- Missing required environment variables
- Incorrect transport type selection
- Typos in server URLs or commands
- Missing file permissions or executable flags
Getting Help
If you’re still experiencing issues:-
Check server documentation
- Review the MCP server’s specific documentation
- Look for known issues or troubleshooting guides
-
Community support
- Join our Discord for community help
- Check GitHub Issues for similar problems

