Skip to main content

Troubleshooting Common Issues

This guide covers the most common problems you'll encounter and how to fix them.

Bundle Issues​

Bundle Shows "Needs Credentials" or "Connection Error"​

Symptom: Your bundle shows "Connection Error" or "Credentials expired" warning

Cause: One or more providers in the bundle don't have credentials configured or have expired credentials.

Fix:

  1. Go to Dashboard → Bundles
  2. Click on the bundle
  3. Look for providers with "Not configured" (red text) or expired credentials
  4. Click "Configure" button next to the provider
  5. In the dialog, click "+ Add New Credential" (or select an existing one)
  6. Credential panel slides in from the right
  7. Complete the OAuth flow or enter your API key
  8. Select a validation tool and click "Validate Now"
  9. Bundle status should update to show the provider is verified

Still not working? See Credential Verification Issues

Bundle Shows "Setup Required"​

Symptom: Bundle status shows "Setup Required" (orange badge)

Cause: Required providers don't have credentials configured yet.

What this means:

  • Bundle has never been configured
  • All required providers need credentials
  • Tools won't be available until credentials are added

Fix:

  1. Open the bundle page
  2. Look at the "Configuration Required" section
  3. For each provider showing "Not configured":
    • Click the "Configure" button
    • Click "+ Add New Credential"
    • Follow the credential setup flow
    • Validate the credential
  4. Once all required providers show "Verified", bundle shows "Ready - Credentials valid"

Bundle Configuration

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:

Credential Issues​

OAuth Flow Opens But Nothing Happens​

Symptom: Clicked "Connect with [Provider]" → OAuth window opens → complete login → window closes → credential panel doesn't reopen or show success

Possible Causes:

1. Pop-up Blocker​

Browser blocked the OAuth window or the return.

Fix:

  • Check browser's address bar for blocked pop-up icon
  • Click to allow pop-ups from mcpbundles.com
  • Try the OAuth flow again
  • Credential panel should reopen automatically after OAuth completes

2. Third-Party Cookies Disabled​

OAuth requires session cookies.

Fix:

  • Chrome/Edge: Settings → Privacy → Third-party cookies → Add exception for mcpbundles.com
  • Firefox: Settings → Privacy → Enhanced Tracking Protection → Add exception
  • Safari: Preferences → Privacy → Uncheck "Block all cookies"
  • Try OAuth flow again

3. Browser Extensions​

Ad blockers or privacy extensions might interfere.

Fix:

  • Disable extensions temporarily (try incognito/private mode)
  • If it works, add mcpbundles.com to extension's whitelist
  • Re-enable extensions

4. OAuth Redirect Loop​

Provider's OAuth sent you back, but MCPBundles didn't capture the token.

Check:

  • Look at browser URL - does it have ?code= or ?error= in it?
  • Open browser console (F12) and check for errors

Fix:

  • Go back to your bundle page
  • The credential panel should reopen automatically
  • If not, click "Configure" → "+ Add New Credential" to try again
  • If you see an error code in the URL, contact the provider's support

5. SessionStorage Cleared​

Browser cleared session data during OAuth.

Fix:

  • Don't close the main MCPBundles tab during OAuth
  • Don't click browser "Clear browsing data" during OAuth
  • Try the flow again - credential panel will reopen after OAuth

Key Feature: The credential panel automatically reopens after OAuth completes! If it doesn't, you may have a browser configuration issue.

Credential Verification Failed​

Symptom: You entered credentials but validation failed with an error message

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, check for line breaks)
  • In the credential panel, update the API key
  • Click "Validate Now" to test again

2. Insufficient Permissions (OAuth)​

Your OAuth token doesn't have the required scopes.

Fix:

  • In the credential panel, click "Connect with [Provider]" again
  • When the OAuth window opens, make sure you approve ALL requested permissions
  • After OAuth completes, the validation tool picker will reopen
  • Select a validation tool and click "Validate Now"

3. API Key Expired or Revoked​

The key is no longer valid on the provider's side.

Fix:

  • Log in to the provider's dashboard
  • Check if the API key is still active
  • Generate a new API key if needed
  • Update it in MCPBundles credential panel
  • Validate again

4. Rate Limit or Temporary Block​

The provider is temporarily blocking requests.

Fix:

  • Wait 5-10 minutes
  • Try validating again with the same validation tool
  • If it persists, check the provider's status page
  • Try a different validation tool (might use a different API endpoint)

5. Wrong Account (OAuth)​

You connected OAuth with the wrong account.

Fix:

  • In the credential panel, click "Connect with [Provider]" again to re-authenticate
  • Make sure you log in with the correct account
  • After OAuth completes, validate the credential

"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:

  1. Go to Dashboard → Providers
  2. Find the provider
  3. Click "Reconnect"
  4. Make sure you approve all permissions in the OAuth flow
  5. Complete the flow
  6. 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:

  1. Go to Dashboard → Providers
  2. Find the provider for that tool
  3. Check if status is "Verified"
  4. If not, reconnect/reverify credentials
  5. For OAuth: tokens might have expired—reconnect
  6. 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:

  1. Make sure you're using ChatGPT Plus or Team (MCP requires paid plan)
  2. Go to Settings → Actions → Add Action
  3. Paste the full URL including https://
  4. Wait 10-20 seconds for validation
  5. 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:

  1. Make sure you're using Cursor 0.40+ (update if needed)
  2. Go to Settings → Features → MCP
  3. If you don't see "MCP", update Cursor
  4. 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:

  1. Check the config file format (must be valid JSON)
  2. Make sure the URL is in quotes
  3. Restart Claude Desktop completely
  4. 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 "Ready - Credentials valid"? 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

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:

Browse the Docs: