README is not clear enough for installation

[Squix]

I tried to install the MCP server in Void by using the url only, without the CONTEXT7_API_KEY header which is marked 'optional'.
However, even if the server was recognized, the LLM couldn't use the tools.

It worked when I signed up on Context7 and supplied the apik key header in my mcp.json.

The CONTEXT7_API_KEY is mandatory to use the hosted version of this MCP. Please tell it in the docs.

[enesgules]

I'm sorry but this is not true, I can use the remote MCP server without the header, you might have encountered a different issue. Could you please retry?

[KikeVen]

I'm sorry, but this is not true, I can use the remote MCP server without the header, you might have encountered a different issue. Could you please retry?

It is true for him.

I saw no announcement about the 'new' configuration; my context7 just stopped working. I had to go around all my clients and update them with an API key. Today, none of them is working.

This was working yesterday after spending some time figuring out what was going on, but today I am getting errors:

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

I find the communication and instruction are poor, and your answer is totally out of place

[enesgules]

Hey @KikeVen , I was just stating a fact, the api key is not mandatory. I'm sorry if I offended you. You didn't have to update any of them, they should all work without an API key. All of my old configs kept working, so there might be a different issue on your end. I'm just trying to understand what that issue is both for you and @Squix so that we can solve it.

We haven't deployed anything yesterday to break your client so again that proves my point. Could you please share more logs from your clients related to our MCP server, we can also schedule a call to further investigate if you'd like.