README
¶
harbor-mcptest-stdio
A minimal MCP stdio server used by the Phase 83g integration test
(test/integration/phase83g_mcp_dev_consumer_test.go). Exposes one
tool — echo — and nothing else.
Test fixture only. Not shipped in releases; not referenced by any
operator path. Built by the integration test via go build into a
tempdir. The binary is the canonical reference for "minimal MCP stdio
server" against which Harbor's dev-binary MCP consumer wiring (Phase
83g — D-150) is exercised end-to-end.
If you're an operator looking for a real stdio MCP server, this is not
it. See examples/harbor.yaml for the mcp_servers[] block that
points at external stdio servers (e.g. via uvx <package>).
Documentation
¶
Overview ¶
harbor-mcptest-stdio is a minimal MCP stdio server used by the integration test. It exposes a single tool — `echo` — and nothing else. Built only by the integration test (via `go build` into a tempdir); never shipped in releases.
The binary's contract is intentionally tiny: prove that Harbor's dev-binary MCP wiring (cmd/harbor/cmd_dev.go::bootDevStack) spawns a real subprocess, opens the MCP session, discovers tools, and registers their descriptors into the catalog. Anything richer than "one tool that echoes its input" would test the SDK, not Harbor's consumer wiring.
Source Files