Troubleshooting Common Issues
This guide covers the most common problems you'll encounter and how to fix them.
Bundle Issues
Bundle Shows "Needs Credentials"
Symptom: Your bundle status shows "Needs Credentials" or "Blocked"
Cause: One or more providers in the bundle don't have credentials configured.
Fix:
- Go to Dashboard → Bundles
- Click on the bundle
- Look for providers with red "Not Connected" badges
- Click "Connect" on each provider
- Follow the OAuth flow or enter your API key
- Wait for verification (usually instant)
- Bundle status should change to "Operational"
Still not working? See Credential Verification Issues
Bundle Shows "Partially Operational"
Symptom: Bundle status is "Partially Operational" (yellow)
Cause: Some tools work, but others are blocked due to missing credentials or failed verification.
What this means:
- Tools that don't require blocked providers will work
- Tools that need blocked providers will fail when called
Fix:
- Check which providers are not connected
- Connect missing providers
- Verify credentials are correct
- Check if optional providers are needed for your use case
Optional providers: If you don't need certain tools, you can leave some providers disconnected.
Tools Disappeared from AI
Symptom: Tools were working, now AI says "I don't see any tools"
Possible Causes:
1. Bundle URL Changed
You might have copied a different bundle URL.
Fix:
- Go to Dashboard → Bundles
- Click the bundle you want to use
- Copy the MCP URL shown
- Update it in your AI settings
- Restart your AI app
2. Bundle Was Disabled
You may have disabled the bundle.
Fix:
- Go to Dashboard → Bundles
- Find the bundle
- Click "Enable" if it shows "Disabled"
3. AI App Needs Restart
MCP connections sometimes need a refresh.
Fix:
- Quit your AI app completely
- Reopen it
- Wait 10-30 seconds for tools to load
4. Network Issue
MCPBundles servers might be unreachable.
Fix:
- Check if you can load https://www.mcpbundles.com
- Check your internet connection
- Try again in a few minutes
Credential Issues
OAuth Flow Opens But Nothing Happens
Symptom: Clicked "Connect with OAuth" → new window opens → completes login → window closes → still says "Not Connected"
Possible Causes:
1. Popup Blocked
Your browser blocked the OAuth callback.
Fix:
- Allow popups for mcpbundles.com
- Try connecting again
2. OAuth Timeout
You took too long to complete the login.
Fix:
- Click "Connect" again
- Complete the OAuth flow faster (within 5 minutes)
3. Incorrect Redirect URI
The OAuth app configuration might be wrong.
Fix:
- This is rare and usually means the provider has an issue
- Contact support with the provider name
Credential Verification Failed
Symptom: You entered credentials but status shows "Verification Failed"
Common Causes:
1. Wrong API Key
You copied the wrong key or it has a typo.
Fix:
- Go back to the provider's website
- Generate a new API key
- Copy it carefully (no extra spaces)
- Paste it again in MCPBundles
- Click "Verify"
2. Insufficient Permissions (OAuth)
Your OAuth token doesn't have the right scopes.
Fix:
- Click "Reconnect" to redo OAuth
- Make sure you approve ALL requested permissions
- Some providers have separate "read" and "write" checkboxes—enable both
3. API Key Expired or Revoked
The key is no longer valid.
Fix:
- Log in to the provider
- Check if the API key is still active
- Generate a new one if needed
- Update it in MCPBundles
4. Rate Limit or Temporary Block
The provider is temporarily blocking requests.
Fix:
- Wait 5-10 minutes
- Try verifying again
- If it persists, check the provider's status page
5. Wrong Account
You connected OAuth with the wrong account.
Fix:
- Click "Disconnect"
- Click "Connect" again
- Use the correct account in the OAuth flow
"Scope Mismatch" Error When Using Tool
Symptom: Tool works in test, but when AI calls it you get "scope mismatch" error
Cause: Your OAuth token is missing required scopes.
Fix:
- Go to Dashboard → Providers
- Find the provider
- Click "Reconnect"
- Make sure you approve all permissions in the OAuth flow
- Complete the flow
- Try the tool again
Example: Smartlead might ask for:
- Read campaigns
- Write campaigns
- Read leads
- Write leads
You must approve ALL of them, not just "Read campaigns."
Tool Execution Issues
Tool Call Fails with "401 Unauthorized"
Symptom: AI tries to call a tool → gets error "401 Unauthorized"
Cause: Credentials are invalid or expired.
Fix:
- Go to Dashboard → Providers
- Find the provider for that tool
- Check if status is "Verified"
- If not, reconnect/reverify credentials
- For OAuth: tokens might have expired—reconnect
- For API keys: generate a new one
Tool Call Fails with "404 Not Found"
Symptom: Tool exists in bundle but returns 404 when called
Possible Causes:
1. Provider API Changed
The external API endpoint changed.
Fix:
- This is a platform issue
- Report it to MCPBundles support
- We'll update the tool definition
2. Resource Doesn't Exist
You're trying to access something that doesn't exist (e.g., campaign ID 999 doesn't exist).
Fix:
- Use
list_campaigns
first to see available IDs - Pass a valid ID to the tool
Tool Call Fails with "Rate Limit Exceeded"
Symptom: Tool works sometimes, then fails with "429 Too Many Requests"
Cause: The external API has rate limits (e.g., 100 requests/hour).
Fix:
- Wait for the rate limit to reset (usually 1 hour)
- Reduce how often you call tools
- Check the provider's documentation for their limits
- Consider upgrading your plan with the provider (not MCPBundles)
Note: MCPBundles doesn't add its own rate limits—these come from the external API providers.
Tool Returns Empty Results
Symptom: Tool runs successfully but returns []
or empty data
Possible Causes:
1. No Data Exists
There's actually nothing to return.
Example: list_campaigns
returns []
if you have no campaigns.
Fix: Create some data in the provider's app first.
2. Filters Too Restrictive
Your query filters out everything.
Example: list_campaigns(status="paused")
returns []
if all campaigns are active.
Fix: Try without filters or use different filter values.
3. Wrong Account
You're connected to a different account than expected.
Fix:
- Check Dashboard → Providers
- See which account is connected
- Reconnect with the correct account if needed
AI Platform Issues
ChatGPT Won't Load MCP URL
Symptom: Added MCP URL in ChatGPT settings → nothing happens
Fix:
- Make sure you're using ChatGPT Plus or Team (MCP requires paid plan)
- Go to Settings → Actions → Add Action
- Paste the full URL including
https://
- Wait 10-20 seconds for validation
- If it fails, copy the URL again (might have extra spaces)
See ChatGPT Integration Guide for detailed steps.
Cursor Can't Find MCP Settings
Symptom: Can't find where to add MCP URL in Cursor
Fix:
- Make sure you're using Cursor 0.40+ (update if needed)
- Go to Settings → Features → MCP
- If you don't see "MCP", update Cursor
- Add URL in the MCP servers section
See Cursor Integration Guide for detailed steps.
Claude Desktop Says "Server Not Responding"
Symptom: Added MCP URL to config file → Claude says server not responding
Fix:
- Check the config file format (must be valid JSON)
- Make sure the URL is in quotes
- Restart Claude Desktop completely
- Check if the URL is reachable in a browser
See Claude Desktop Integration Guide for config examples.
General Debugging Steps
If you're stuck, try these in order:
1. Check Bundle Status
- Dashboard → Bundles → [Your Bundle]
- Is it "Operational"? If not, fix credentials first
2. Check Provider Status
- Dashboard → Providers
- Are all needed providers "Verified"? If not, reconnect them
3. Restart Your AI
- Quit completely (not just close window)
- Reopen
- Wait 30 seconds
4. Try a Different Tool
- If one tool fails, try another from the same bundle
- Helps isolate if it's a tool-specific issue or bundle-wide
5. Check the Provider's Website
- Log in to the external service (Smartlead, GitHub, etc.)
- Make sure the data exists
- Make sure your API key/account is active
6. Test in Dashboard
- Some bundles have a "Test" button
- Try running the tool directly in MCPBundles
- This bypasses the AI and tests the tool directly
7. Check for Maintenance
- Visit https://status.mcpbundles.com (if we have one)
- Or check our Twitter/status page
- We'll announce planned downtime
Error Messages Reference
"Bundle not found"
Cause: The bundle ID in your URL is wrong or the bundle was deleted.
Fix: Copy a fresh URL from your Dashboard.
"Authentication required"
Cause: Provider credentials are missing or invalid.
Fix: Connect/verify credentials in Dashboard → Providers.
"Provider verification failed"
Cause: Credentials are wrong or don't have proper permissions.
Fix: Double-check API key or redo OAuth with all scopes.
"Tool not found in bundle"
Cause: You're trying to call a tool that doesn't exist in this bundle.
Fix: Check the bundle's tool list in the dashboard. The AI might be hallucinating tool names.
"Insufficient permissions"
Cause: OAuth token lacks required scopes.
Fix: Reconnect provider and approve all permissions.
"Provider API error"
Cause: The external API returned an error.
Fix: Check the error message details. Might be rate limit, bad parameters, or provider downtime.
"Invalid tool arguments"
Cause: The AI called the tool with wrong parameter types or values.
Fix: Check tool documentation for correct parameter format. This is usually an AI hallucination issue—prompt the AI more clearly.
Still Having Issues?
Contact Support:
- Email: help@mcpbundles.com
- Include:
- Bundle name or ID
- Provider name
- Tool name (if specific to one tool)
- Error message (exact text)
- What you've tried already
Check the FAQ:
- Frequently Asked Questions
- Might have your answer
Browse the Docs: