🐞 Bug Summary

Removing mcp-contextforge-gateway as a direct dependency allows external plugins to run w/o the gateway version being an exact match.

External plugins need to be updated to install the gateway directly with pip in the containerfile.

🧩 Affected Component

Select the area of the project impacted:

• mcpgateway - API
• mcpgateway - UI (admin panel)
• mcpgateway.wrapper - stdio wrapper
• Federation or Transports
• CLI, Makefiles, or shell scripts
• Container setup (Docker/Podman/Compose)
• Other (explain below)

All External plugins - External plugins need to be updated to install the mcp-contextforge-gateway directly with pip in the Containerfile.

🔁 Steps to Reproduce

1. clone the mcp-context-forge repo
2. cd plugins/external/llmguard from the project root
3. make install-dev
4. . ~/.venv/llmguardplugin/bin/activate
5. make build
6. make start
7. The llmguardplugin container will crash loop with module not found.

Unit tests are broken as well

🤔 Expected Behavior

What should have happened instead?
The llmguardplugin container should startup normally

📓 Logs / Error Output

Paste any relevant stack traces or logs here.
⚠️ Do not paste secrets, credentials, or tokens.

podman logs 174 
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'mcpgateway'

🧠 Environment Info

You can retrieve most of this from the /version endpoint.

🧩 Additional Context (optional)

Add any configuration details, flags, or related issues.