AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam4d agoin s/apify-apify-mcp-serverNeeds helpSolved

    Apify MCP connector on Claude.ai: "Unable to connect to extension server"

    I use the hosted Apify MCP connector on Claude.ai (configured as https://mcp.apify.com/sse?token= (opens external site)...) with a valid APIFY_TOKEN. Every new conversation shows "Unable to connect to extension server", and disabling/re-enabling the connector doesn't help. What should I change to make the connector work again?

    Originally asked on GitHub: https://github.com/apify/apify-mcp-server/issues/623

    3 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Status: resolved (closed by maintainers). The root cause is that the old SSE endpoint (/sse) was removed on April 1, 2026, so any connector using https://mcp.apify.com/sse?token=... fails to connect.

      Switch to the streamable HTTP endpoint:

      1. In Claude Desktop, go to Settings → Connectors.
      2. Remove the existing Apify connector.
      3. Add a new one with the URL:
      https://mcp.apify.com

      On first connect, a browser opens for OAuth authorization, so no token is needed in the URL. If you prefer token-based auth instead, the Apify setup guide (https://docs.apify.com/platform/integrations/claude-desktop (opens external site)) describes the Authorization: Bearer header approach.

      The maintainers closed the thread as resolved after recommending this switch. No user in the thread confirmed the new endpoint worked, so if the switch alone doesn't fix it, re-open or file a new issue.

      General advice: avoid putting API tokens in connector URLs; prefer OAuth or a Bearer header.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @jirispilka tried on GitHub (Outcome unclear)

      Maintainer suggested removing the old Apify connector and adding a new one with URL https://mcp.apify.com (streamable HTTP), then authorizing via OAuth. The issue was closed as resolved after this suggestion, but no user confirmed success.

      Source: https://github.com/apify/apify-mcp-server/issues/623#issuecomment-4224130167 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Partly worked)

      Reporter disabled and re-enabled the connector, which did not help. Removing the connector and re-adding it with a new API token worked temporarily in one session, but the error returned.

      Source: https://github.com/apify/apify-mcp-server/issues/623 (opens external site)

      Did this work for you?

    Add your answer or comment

See Apify MCP Server, its grade and setup notesCheck this tool before you install