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: .pre-commit-config.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ repos:
89
89
- id: forbid-ai-stock-phrases
90
90
name: ❌ Forbid AI Stock Phrases
91
91
description: Prevents common AI-generated phrases from being committed.
92
-
entry: '(?i)(source=chatgpt.com|turn0search0|filecite|as an ai language model|i am an ai developed by|this response was generated by|i don''t have real-time information|i don''t have access to real-time|i can''t browse the internet|i cannot browse the internet|my knowledge cutoff|my training data|i''m not able to access|i don''t have the ability to)'
92
+
entry: '(?i)(source=chatgpt.com|turn0search0|filecite|unchanged|as an ai language model|i am an ai developed by|this response was generated by|i don''t have real-time information|i don''t have access to real-time|i can''t browse the internet|i cannot browse the internet|my knowledge cutoff|my training data|i''m not able to access|i don''t have the ability to)'
The `mcpgateway.wrapper` lets you connect to the gateway over **stdio**, while retaining authentication using the JWT token when the wrapper connect to a remote gateway. You should run this from a MCP client. You can test this from a shell with:
export MCP_WRAPPER_LOG_LEVEL=DEBUG # or OFF to disable logging
192
+
193
+
# Run the wrapper from the installed module
194
+
python3 -m mcpgateway.wrapper
195
+
```
176
196
177
-
The mcpgateway-wrapper lets you connect to the gateway over stdio, while retaining authentication using the JWT token when the wrapper connect to a remote gateway. You should run this from a MCP client. You can test this from a shell with:
run --directory mcpgateway-wrapper mcpgateway-wrapper
187
-
# You'll see a message similar to: Installed 21 packages in 6ms - it's now expecting input from an MCP client
206
+
python3 -m mcpgateway.wrapper
188
207
```
189
208
190
-
Testing `mcpgateway-wrapper` by hand:
209
+
**Testing `mcpgateway-wrapper` by hand:**
191
210
192
211
Because the wrapper speaks JSON-RPC over stdin/stdout, you can interact with it using nothing more than a terminal or pipes.
193
212
@@ -240,81 +259,135 @@ Expected:
240
259
241
260
```
242
261
243
-
### Running from a MCP Client
244
262
245
-
The `mcpgateway-wrapper` should be used with an MCP Client that does not support SSE. You can configure it as such.
263
+
### 🧩 Running from an MCP Client (`mcpgateway.wrapper`)
264
+
265
+
The `mcpgateway.wrapper` exposes everything your Gateway knows about over **stdio**, so any MCP client that *can't* (or *shouldn't*) open an authenticated SSE stream still gets full tool-calling power.
266
+
267
+
> **Remember** to substitute your real Gateway URL (and server ID) for `http://localhost:4444/servers/1`.
268
+
> When inside Docker/Podman, that often becomes `http://host.docker.internal:4444/servers/1` (macOS/Windows) or the gateway container's hostname (Linux).
<summary><strong>📦 pipx (one-liner install & run)</strong></summary>
246
291
247
-
Remember to replace the `MCP_SERVER_CATALOG_URL` with the actual URL of your MCP Gateway. Consider container networking - when running this via a container engine, this should represent a network accessible from Docker/Podman, ex: `http://host.docker.internal:4444/servers/1`
292
+
```bash
293
+
# Install gateway package in its own isolated venv
You have a number of options for running the wrapper. Docker/Podman, to run it from the container. `uvx`, `uvenv` or `pipx` to run it straight from pip. Or just running it with Python from a local directory. Adjust your command accordingly.
302
+
**Claude Desktop JSON** (uses the host Python that pipx injected):
Restart Claude Desktop (exiting from system tray). Go back to `File > Settings > Developer > Edit Config` to check on your configuration and view the logs.
377
+
</details>
378
+
379
+
---
380
+
381
+
### 🚀 Using with Claude Desktop (or any GUI MCP client)
2. Paste one of the JSON blocks above (Docker / pipx / uvenv).
385
+
3. Restart the app so the new stdio server is spawned.
386
+
4. Open logs in the same menu to verify `mcpgateway-wrapper` started and listed your tools.
387
+
388
+
Need help? See:
316
389
317
-
For more details, see the [Claude MCP quickstart](https://modelcontextprotocol.io/quickstart/server). For issues, see [MCP Debugging](https://modelcontextprotocol.io/docs/tools/debugging).
0 commit comments