Skip to main content

​
Common issues

Verify you are using the correct endpoint URL:Check that your network allows outbound HTTPS connections. If you are behind a corporate firewall or VPN, ensure app.swoop.it is not blocked.
The OAuth sign-in opens a browser window. If the flow doesn’t complete:
  • Check that your browser is not blocking pop-ups for the sign-in page
  • Try clearing cookies for app.swoop.it and signing in again
  • Ensure mcp-remote is up to date: npx mcp-remote@latest
  • If the browser window doesn’t open, try copying the URL from the terminal and opening it manually
If your API key is not accepted:
  • Verify the key starts with ak_
  • Check the key has not been revoked in the Swoop dashboard
  • Ensure the Authorization header format is correct: Bearer ak_your_key_here
  • Create a new key if the issue persists
Presentation generation can take 30-60 seconds. The server sends progress heartbeats every 10 seconds to keep the connection alive. If you still experience timeouts:
  • Ensure your MCP client supports long-running operations
  • Check that any proxy or load balancer between you and the server has a timeout of at least 120 seconds
  • Try a simpler prompt to verify connectivity
The Swoop MCP server allows cross-origin requests from all origins. If you see CORS errors:
  • Ensure you are using the correct endpoint URL
  • Check that your browser extensions are not modifying request headers
  • Try in a private/incognito browser window

​
Testing with MCP Inspector

Use the MCP Inspector to debug connection and authentication issues:
1

Launch the inspector

npx @modelcontextprotocol/inspector
2

Configure the connection

In the browser UI:
  • Set Transport type to Streamable HTTP
  • Set URL to https://app.swoop.it/api/mcp
3

Authenticate and test

Complete the OAuth flow when prompted, then browse available tools and test ask_swoopAgent with a sample prompt.