You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,9 +118,11 @@ ContextForge MCP Gateway is a feature-rich gateway, proxy and MCP Registry that
118
118
119
119
## 🚀 Overview & Goals
120
120
121
-
**ContextForge MCP Gateway** is a production-grade gateway, registry, and proxy that sits in front of any [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server or REST API-exposing a unified endpoint for all your AI clients.
121
+
**ContextForge MCP Gateway** is a gateway, registry, and proxy that sits in front of any [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server or REST API-exposing a unified endpoint for all your AI clients.
122
122
123
-
It supports:
123
+
**⚠️ Caution**: The current release (0.3.1) is considered alpha / early beta. It is not production-ready and should only be used for local development, testing, or experimentation. Features, APIs, and behaviors are subject to change without notice. **Do not** deploy in production environments without thorough security review, validation and additional security mechanisms. Many of the features required for secure, large-scale, or multi-tenant production deployments are still on the [project roadmap](https://ibm.github.io/mcp-context-forge/architecture/roadmap/) - which is itself evolving.
124
+
125
+
It currently supports:
124
126
125
127
* Federation across multiple MCP and REST services
126
128
* Virtualization of legacy APIs as MCP-compliant tools and servers
@@ -133,6 +135,8 @@ It supports:
133
135
134
136
For a list of upcoming features, check out the [ContextForge MCP Gateway Roadmap](https://ibm.github.io/mcp-context-forge/architecture/roadmap/)
135
137
138
+
**⚠️ Important**: MCP Gateway is not a standalone product - it is an open source component with **NO OFFICIAL SUPPORT** from IBM or its affiliates that can be integrated into your own solution architecture. If you choose to use it, you are responsible for evaluating its fit, securing the deployment, and managing its lifecycle. See [SECURITY.md](./SECURITY.md) for more details.
139
+
136
140
---
137
141
138
142
<details>
@@ -848,6 +852,14 @@ make lint # optional: run style checks (ruff, mypy, etc.)
848
852
849
853
### Containerised (self-signed TLS)
850
854
855
+
## Container Runtime Support
856
+
857
+
This project supports both Docker and Podman. The Makefile automatically detects
858
+
which runtime is available and handles image naming differences.
859
+
860
+
### Auto-detection
861
+
```bash
862
+
make container-build # Uses podman if available, otherwise docker
0 commit comments