mcp-go-sse

This MCP server exposes an MCP interface over Server-Sent Events (SSE) using a Go binary. It is built from the mcp-go-sse-server source and can serve prompts, tools, and resources to MCP clients. To run it, build the project and start the resulting binary with the SSE transport enabled and a base URL for clients to connect to. The README examples show how the server is typically launched, with the server listening for SSE connections at the specified base URL. The repository notes a real-use branch that demonstrates integration with external systems (e.g., reading from PostgreSQL and publishing to a NATS channel). When running locally, you can start with a base URL like http://localhost and switch to https in production, ensuring the server’s base URL matches your deployment.

Prerequisites:

• Go tooling installed (go version 1.17+ recommended)
• Access to the repository with the mcp-go-sse-server source

Installation steps:

1. Clone the repository: git clone <repository-url> cd mcp-go-sse-server

2. Build the Go SSE server: go build .

3. Run the server (example locally): ./mcp-go-sse-server --transport sse --baseurl http://localhost

4. (Optional) Run with HTTPS in production by configuring baseURL to an HTTPS endpoint and providing any necessary TLS configuration as required by your deployment environment.

Tips and notes:

• The server uses SSE for transport. Ensure your firewall and reverse proxy configurations allow SSE streams.
• The README indicates support for a real-use scenario that interfaces with PostgreSQL and publishes to NATS on a separate branch; you can explore that branch for integration examples.
• When deploying, you can switch the base URL to your production domain (e.g., https://mcp.example.com) and use --omitPort if your reverse proxy handles the port externally.
• If you need to customize environment variables, you can edit the env section in mcp_config to pass necessary configuration keys to the Go binary.
• If encountering connection issues, verify that the transport is set to SSE and that the base URL in clients matches the server's listening address.