Connection problems with all my clients

[KikeVen]

I had to update all my clients a few days ago because Context7 stopped working suddenly.

	"context7": {
		"type": "http",
		"url": "https://mcp.context7.com/mcp",
		"headers": {
			"CONTEXT7_API_KEY": "API-KEY"
		}

VS Code:

2025-09-08 13:49:26.987 [info] Connection state: Running
2025-09-08 13:49:27.638 [info] Error connecting to https://mcp.context7.com/mcp for async notifications, will retry
2025-09-08 13:49:27.640 [info] Connection state: Error Error sending message to https://mcp.context7.com/mcp: TypeError: fetch failed
2025-09-08 13:49:30.317 [info] Stopping server context7
2025-09-08 13:49:30.320 [info] Starting server context7
2025-09-08 13:49:30.320 [info] Connection state: Starting
2025-09-08 13:49:30.324 [info] Starting server from LocalProcess extension host

Gemini:

ℹConfigured MCP servers:

  🔴 context7 - Disconnected (0 tools cached)
    No tools or prompts available

---

Fast forward after having to log in to the Context7 website, and come to find out there is a new configuration.

	"context7": {
		"type": "http",
		"url": "https://mcp.context7.com/mcp",
		"headers": {
			"CONTEXT7_API_KEY": "Bearer API-KEY"
		}

Remember to add Bearer space and your API-Key.

[enesgules]

Hey @KikeVen sorry for your bad experience. The issue here is probably something else. The Bearer part is removed from the headers always, if you don't want to take my word for it you can check the implementation in the repo, so that being an issue before might either be related to your client, or there was a connection issue and now that is fixed. We are working on improving the remote MCP server's capacity but in the mean time could you please retry without Bearer to see my point. Thanks.

[enesgules]

For the record, if the API key is invalide, we return Unauthorized error, so without the Bearer part you should have seen that since the entire string would be broken if we removed chars from it. But the fetch error tells me this issue is not related to the usage of API key but rather establishing a connection.

[enesgules]

Please let us know if you want to follow up further