|
1 |
| -# Media Kit |
| 1 | +# 🧰 Media Kit |
2 | 2 |
|
3 |
| -A one-stop kit for bloggers & press: |
| 3 | +Everything you need to write about **[ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge)**—assets, ready-to-use copy, badges, images, and quick-start commands. |
4 | 4 |
|
5 |
| -- **Sample Announcement** |
6 |
| - A ready-made blog post template |
| 5 | +--- |
7 | 6 |
|
8 |
| -- **Brand Guidelines** |
9 |
| - Logo usage, colors & fonts |
| 7 | +## 🤔 What is MCP (Model Context Protocol)? |
10 | 8 |
|
11 |
| -- **Logos** |
12 |
| - SVG/PNG assets |
| 9 | +[MCP](https://modelcontextprotocol.io/introduction) is an open-source protocol released by Anthropic in **November 2024** that lets AI agents communicate with external tools through a standard JSON-RPC envelope. It's often described as the "USB-C of AI"—a universal connector for language models. |
13 | 10 |
|
14 |
| -- **Badges** |
15 |
| - Markdown badges & buttons |
| 11 | +It's widely supported by GitHub Copilot, Microsoft Copilot, AWS Bedrock, Google Cloud AI, IBM watsonx, and **15,000+ servers** in the community. |
16 | 12 |
|
17 |
| -- **Social Templates** |
18 |
| - Pre-written tweets & LinkedIn copy |
| 13 | +### ⚡ Why it matters |
19 | 14 |
|
20 |
| -- **Images** |
21 |
| - Hero banners & screenshots |
| 15 | +- ✅ Standardized interface contracts via typed JSON Schema |
| 16 | +- ✅ Supported across the ecosystem — GitHub/Microsoft Copilot, AWS Bedrock, Google Cloud AI, IBM watsonx, AgentBee, LangChain, CrewAI, and more |
| 17 | +- ✅ Strong ecosystem - **15,000+** MCP-compatible servers and multiple clients, with announcements from multiple major vendors |
| 18 | + |
| 19 | +### ❌ Current challenges |
| 20 | + |
| 21 | +- ❌ Fragmented transports: STDIO, SSE, HTTP — with some methods already deprecated |
| 22 | +- ❌ Inconsistent authentication: none, JWT, OAuth |
| 23 | +- ❌ Operational overhead: managing endpoints, credentials, retries, and logs for each tool |
| 24 | +- ❌ Version mismatch: clients and servers may support different MCP versions |
| 25 | + |
| 26 | +--- |
| 27 | + |
| 28 | +## 💡 Why [ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge)? |
| 29 | + |
| 30 | +> **Problem:** Most teams build one-off adapters for each tool or model, leading to maintenance burden and slow development. |
| 31 | +
|
| 32 | +[ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge) solves this by proxying all MCP and REST tool servers through a **single HTTPS + JSON-RPC endpoint**, with discovery, security, and observability built in. |
| 33 | + |
| 34 | +It lets you create Virtual Servers - remixing tools/prompts/resources from multiple servers, introduce strong Auth - and change protocol versions on the fly. It lets you easily create new MCP Servers without having to write any code - by proxing existing REST services. |
| 35 | + |
| 36 | +And is readily available as open source, published a container image and as a Python module published on PyPi - so you can get started with a single command - and scale all the way up to multi-regional Kubernetes clusters. |
| 37 | + |
| 38 | +| Pain Point | How Gateway Solves It | |
| 39 | +|--------------------------------------|--------------------------------------------------| |
| 40 | +| Transport fragmentation (STDIO/SSE/HTTP) | Unifies everything under HTTPS + JSON-RPC | |
| 41 | +| DIY wrappers & retry logic | Automatic, schema-validated retry handling | |
| 42 | +| Weak auth layers | Built-in JWT (or OAuth) & rate limiting | |
| 43 | +| No visibility | Per-call and per-server metrics & logging | |
| 44 | +| Onboarding difficulties | Built-in admin UI for tools, prompts, and resources | |
| 45 | + |
| 46 | + |
| 47 | + |
| 48 | +--- |
| 49 | + |
| 50 | +## 📑 Sample Announcements |
| 51 | + |
| 52 | +???+ "📣 Non-Technical Post" |
| 53 | + ### Meet ContextForge MCP Gateway: Simplify AI Tool Connections |
| 54 | + |
| 55 | + Building AI agents should be easy—but each tool speaks a different dialect. |
| 56 | + |
| 57 | + **[ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge)** is a universal hub: one secure endpoint that discovers your tools and works seamlessly with Copilot, CrewAI, LangChain, and more. |
| 58 | + |
| 59 | + > "What should be simple often becomes a debugging nightmare. The ContextForge MCP Gateway solves that." — Mihai Criveti |
| 60 | + |
| 61 | + **Try it in 60 seconds:** |
| 62 | + ```bash |
| 63 | + docker run -d --name mcpgateway \ |
| 64 | + -p 4444:4444 \ |
| 65 | + -e JWT_SECRET_KEY=YOUR_KEY \ |
| 66 | + ghcr.io/ibm/mcp-context-forge:latest |
| 67 | + ``` |
| 68 | + |
| 69 | + Please ⭐ the project on GitHub if you find this useful, it helps us grow! |
| 70 | + |
| 71 | +???+ "🛠️ Technical Post" |
| 72 | + ### Introducing ContextForge MCP Gateway: The Missing Proxy for AI Agents and Tools |
| 73 | + |
| 74 | + **[ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge)** normalizes STDIO, SSE, REST, and HTTP MCP servers into one HTTPS + JSON-RPC interface with full MCP support. |
| 75 | + |
| 76 | + It includes schema-validated retries, JWT auth, and a built-in catalog UI. |
| 77 | + |
| 78 | + **Docker:** |
| 79 | + ```bash |
| 80 | + docker run -d --name mcpgateway \ |
| 81 | + -p 4444:4444 \ |
| 82 | + -e JWT_SECRET_KEY=YOUR_KEY \ |
| 83 | + ghcr.io/ibm/mcp-context-forge:latest |
| 84 | + ``` |
| 85 | + |
| 86 | + **PyPI:** |
| 87 | + ```bash |
| 88 | + pip install mcp-gateway |
| 89 | + mcpgateway --host 0.0.0.0 --port 4444 |
| 90 | + ``` |
| 91 | + |
| 92 | + Please ⭐ the project on GitHub if you find this useful, it helps us grow! |
| 93 | + |
| 94 | +--- |
| 95 | + |
| 96 | +???+ "🛠️ Connect Cline VS Code Extension to ContextForge MCP Gateway" |
| 97 | + |
| 98 | + > A great idea is to create posts, videos or articles on using specific clients or with MCP Gateway. |
| 99 | + Provide details on how to run and register a number of useful MCP Servers, adding them to the gateway, then using specific clients to connect. For example, Visual Studio Cline, GitHub Copilot, Langchain, etc. Example: |
| 100 | + |
| 101 | + ### Connect your Cline extension to MCP Gateway |
| 102 | + |
| 103 | + **[ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge)** offers a unified HTTPS + JSON‑RPC endpoint for AI tools, making integration seamless—including with **Cline**, a VS Code extension that supports MCP. |
| 104 | + |
| 105 | + **Start the Gateway (Docker):** |
| 106 | + ```bash |
| 107 | + docker run -d --name mcpgateway \ |
| 108 | + -p 4444:4444 \ |
| 109 | + -e JWT_SECRET_KEY=YOUR_KEY \ |
| 110 | + ghcr.io/ibm/mcp-context-forge:latest |
| 111 | + ``` |
| 112 | + |
| 113 | + **Or install via PyPI:** |
| 114 | + |
| 115 | + ```bash |
| 116 | + pip install mcp-gateway |
| 117 | + mcpgateway --host 0.0.0.0 --port 4444 |
| 118 | + ``` |
| 119 | + |
| 120 | + ⭐ Enjoying this? Leave a star on GitHub! |
| 121 | + |
| 122 | + --- |
| 123 | + |
| 124 | + #### 🔍 What is Cline? |
| 125 | + |
| 126 | + [Cline](https://cline.bot/) is a powerful AI coding assistant for VS Code. It supports MCP, allowing it to discover and use tools provided through MCP Gateway. |
| 127 | + |
| 128 | + --- |
| 129 | + |
| 130 | + #### 🔐 Set up JWT Authentication |
| 131 | + |
| 132 | + In your Cline settings, add an MCP server: |
| 133 | + |
| 134 | + ```json |
| 135 | + { |
| 136 | + "name": "MCP Gateway", |
| 137 | + "url": "http://localhost:4444", |
| 138 | + "auth": { |
| 139 | + "type": "bearer", |
| 140 | + "token": "<YOUR_JWT_TOKEN>" |
| 141 | + } |
| 142 | + } |
| 143 | + ``` |
| 144 | + |
| 145 | + Enable the server in Cline—you should see a green "connected" indicator when authentication succeeds. |
| 146 | + |
| 147 | + --- |
| 148 | + |
| 149 | + #### 🚀 Using MCP Tools in Cline |
| 150 | + |
| 151 | + With the connection live, Cline can: |
| 152 | + |
| 153 | + * Automatically list tools exposed by the Gateway |
| 154 | + * Use simple prompts to invoke tools, e.g.: |
| 155 | + |
| 156 | + ``` |
| 157 | + Run the `list_files` tool with path: "./src" |
| 158 | + ``` |
| 159 | + * Display results and JSON output directly within the VS Code interface |
| 160 | + |
| 161 | + Try it yourself—and don't forget to ⭐ the project at [ContextForge MCP Gateway](https://github.com/IBM/mcp-context-forge)! |
| 162 | + |
| 163 | + |
| 164 | +## 🖼️ Logo & Images |
| 165 | + |
| 166 | +| Asset | URL | |
| 167 | +|-------|-----| |
| 168 | +| Transparent PNG logo | `https://ibm.github.io/mcp-context-forge/logo.png` | |
| 169 | +| Hero demo GIF | `https://ibm.github.io/mcp-context-forge/images/mcpgateway.gif` | |
| 170 | +| Architecture overview | [SVG](https://ibm.github.io/mcp-context-forge/images/mcpgateway.svg) | |
| 171 | + |
| 172 | +--- |
| 173 | + |
| 174 | +## 📣 Social Snippets |
| 175 | + |
| 176 | +**Tweet / X** |
| 177 | + |
| 178 | +!!! example "Twitter / X" |
| 179 | + 🚀 ContextForge MCP Gateway is now open source! One endpoint to unify & secure AI-tool connections (STDIO, SSE, REST). Give it a spin and drop a ⭐ → https://github.com/IBM/mcp-context-forge #mcp #ai #tools |
| 180 | + |
| 181 | +**LinkedIn** |
| 182 | + |
| 183 | +!!! example |
| 184 | + Thrilled to share **ContextForge MCP Gateway**—an open-source hub that turns fragmented AI-tool integrations into a single secure interface with discovery, observability, and a live catalog UI. Check it out on GitHub and leave us a star ⭐! |
| 185 | + `#mcp #ai #tools` |
| 186 | + |
| 187 | +!!! tip Examples Posts |
| 188 | + See [Social](../social/index.md) for example articles and social media posts - and add your own there once published! |
0 commit comments