What runtime or dependencies are required?
The server requires Go to build and run. It depends on the mark3labs/mcp-go library internally.
@davidferlay
Basic information
A simple MCP server exposed via SSE with examples tools, resources and prompts
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A simple MCP server exposed via SSE (Server-Sent Events) with example tools, resources, and prompts. It is based on the example from the mark3labs/mcp-go GitHub repository. The server is built with Go and is intended for developers experimenting with or testing the Model Context Protocol.
Build the binary with go build . and run it with ./mcp-golang-http-server --transport sse --baseurl http://localhost. For a public deployment, use --baseurl https://mcp.example.com and optionally add the --omitPort flag to exclude the port from the URL.
--baseurl flag--omitPort flag for cleaner URLsThe server requires Go to build and run. It depends on the mark3labs/mcp-go library internally.
It uses SSE (Server-Sent Events) transport, specified via the `--transport` flag.
Use the `--baseurl` flag when running the server, for example `--baseurl http://localhost` or `--baseurl https://mcp.example.com`.
Yes, add the `--omitPort` flag to exclude the port from the server’s URL.
The server is a modified version of the everything example from the mark3labs/mcp-go repository.
A curated list of references for MLOps
不止于 CSS

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.

See and control a real Windows PC you own — from any MCP client, locally or remotely. Observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH: your machine, your key.

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Comments