Skip to content
Back to search

mcp-gateway

A gateway demo for MCP SSE Server

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/lightconetech--mcp-gateway/badge.svg)](/listings/lightconetech--mcp-gateway)

HTML

<a href="/listings/lightconetech--mcp-gateway"><img src="/api/listings/lightconetech--mcp-gateway/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install the gateway globally using npm:

npm install -g @mcphub/gateway

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 123 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # MCP Server Gateway
  2. A gateway service that bridges the stdio-based Model Context Protocol (MCP) implementation in Claude Desktop with HTTP/SSE-based MCP servers. This solves the protocol compatibility gap since Claude Desktop currently only supports stdio-based MCP servers. See the discussion [here](https://github.com/orgs/modelcontextprotocol/discussions/16).
  3. ## Why This Gateway?
  4. Claude Desktop App currently only supports stdio protocol for MCP servers, while many MCP servers use HTTP with Server-Sent Events (SSE) transport. This gateway acts as a protocol translator, allowing Claude Desktop to communicate with any HTTP/SSE MCP server by:
  5. 1. Accepting stdio input from Claude Desktop
  6. 2. Converting and forwarding requests to HTTP/SSE MCP servers
  7. 3. Converting SSE responses back to stdio format for Claude Desktop
  8. ## Installation
  9. Install the gateway globally using npm:
  10. ```bash
  11. npm install -g @mcphub/gateway
  12. ```
  13. ## Configuration
  14. ### 1. Find the Gateway Path
  15. After installation, find where npm installed the gateway using these commands:
  16. ```bash
  17. # This shows the root directory of global packages
  18. npm root -g
  19. # The gateway will be located at:
  20. <npm_global_root>/@mcphub/gateway/dist/src/mcphub-gateway.js
  21. ```
  22. Common global package locations:
  23. - macOS (Homebrew Node): `/opt/homebrew/lib/node_modules/@mcphub/gateway/dist/src/mcphub-gateway.js`
  24. - macOS (default): `/usr/local/lib/node_modules/@mcphub/gateway/dist/src/mcphub-gateway.js`
  25. - Windows: `%AppData%\npm\node_modules\@mcphub\gateway\dist\src\mcphub-gateway.js`
  26. Verify the installation and path:
  27. ```bash
  28. npm list -g @mcphub/gateway
  29. ```
  30. ### 2. Configure Claude Desktop
  31. Create or update your Claude Desktop configuration file:
  32. #### On macOS
  33. Location: `~/Library/Application Support/Claude Desktop/config.json`
  34. #### On Windows
  35. Location: `%APPDATA%\Claude Desktop\config.json`
  36. Add this configuration (using the path you found in step 1):
  37. ```json
  38. {
  39. "mcpServers": {
  40. "server-name": {
  41. "command": "node",
  42. "args": ["/opt/homebrew/lib/node_modules/@mcphub/gateway/dist/src/mcphub-gateway.js"]
  43. }
  44. }
  45. }
  46. ```
  47. Note: Replace the path in `args` with your actual path from step 1.
  48. ### 3. Configure MCP Server Connection
  49. The gateway uses an environment variable to specify which MCP server to connect to:
  50. ```bash
  51. # Set the MCP server URL (optional)
  52. export MCP_SERVER_URL=https://your-mcp-server.com/api/mcp
  53. ```
  54. By default, the gateway connects to the MCP Hub server at `https://server.mcphub.ai/api/mcp`, which provides access to various pre-configured MCP services.
  55. ### 4. Start Claude Desktop
  56. Start or restart Claude Desktop to apply the changes.
  57. ## Troubleshooting
  58. 1. If you can't find the gateway path:
  59. ```bash
  60. # List all global packages and look for @mcphub/gateway
  61. npm list -g
  62. # Or specifically check the gateway
  63. npm list -g @mcphub/gateway
  64. ```
  65. 2. Verify your Node.js installation:
  66. ```bash
  67. # Check Node version
  68. node --version
  69. # Check npm version
  70. npm --version
  71. ```
  72. 3. Common issues:
  73. - If using Homebrew on macOS, make sure Node.js is properly linked:
  74. ```bash
  75. brew doctor
  76. brew link node
  77. ```
  78. - If you get permission errors, you might need to use `sudo` for the installation
  79. ## License
  80. [Apache 2.0 License](LICENSE)
  81. ## Support
  82. If you encounter any issues or have questions:
  83. - File an issue on GitHub
  84. ## Contributing
  85. Contributions are welcome! Please feel free to submit a Pull Request.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.