fix: simple-chatbot env variable

[QIN2DIM]

Motivation and Context

Fix a bug in reading environment variables in the simple-chatbot demo program.

How Has This Been Tested?

re-run uv run main.py

Breaking Changes

No

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[Kludex]

Does it say somewhere that it should be Groq?

[QIN2DIM]

@Kludex Hi,
I see GROQ_API_KEY in .env.example and the corresponding code used in get_response, there's nothing that has to say it has to be GROQ_API_KEY, just that it needs to be consistent on both sides or else os.getenv('xx') won't get the configuration.

python-sdk/examples/clients/simple-chatbot/mcp_simple_chatbot/.env.example

Line 1 in 9ae4df8

GROQ_API_KEY=gsk_1234567890

python-sdk/examples/clients/simple-chatbot/mcp_simple_chatbot/main.py

Line 238 in 9ae4df8

url = "https://api.groq.com/openai/v1/chat/completions"

[dsp-ant]

this is fixed by changing the env variable in .env.example