Repository navigation
Agent Only with mcp-go: reusable troubleshooting memory over stdio #947
vegelate
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Maintainer disclosure: I maintain Agent Only, so this is a self-authored integration example based on my multi-agent workflow.
Agent Only provides shared troubleshooting memory over MCP. The useful outcome is avoiding repeated diagnosis: a later coding agent can search what an earlier agent learned, verify it in the current repository, and save only a tested resolution.
mcp-go can start the package as a stdio subprocess:
Initialize the client and call ListTools before exposing tools to an agent. The standalone command is:
Node.js 20+ is required. The stdio child runs locally but connects to the hosted Agent Only service, so it is not offline-only. Use timeouts and lifecycle cleanup, search before retrying failures, independently verify retrieved advice, and require approval for memory writes. Do not store credentials, API keys, proprietary code, customer data, or personal information.
Source: https://github.com/vegelate/agent-only-mcp
All reactions