Repository navigation
feat(mcp): add --json mode to pipeboard mcp - #15
Merged
Merged
Conversation
Adds a --json flag to pipeboard mcp that emits a clean structured envelope
on stdout and suppresses status messages. The MCP content[].text wrapper
is auto-unwrapped and parsed as JSON when possible, so callers no longer
need to hunt for the start of the JSON in the output or double-parse
content[0].text themselves.
Success: {"ok": true, "data": <parsed>}
Tool-level error (isError=true): {"ok": false, "error": "...", "data": "..."} + exit 1
Transport/auth error: {"ok": false, "error": "..."} + exit 1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
--jsonpersistent flag onpipeboard mcp(applies to bothtools-listandtools-call).{.content[].textwrapper and parses inner JSON when possible, so callers no longer need to double-parse.Shape
{"ok": true, "data": <parsed>}isError: true):{"ok": false, "error": "...", "data": "..."}+ exit 1{"ok": false, "error": "..."}+ exit 1tools-list --json:{"ok": true, "total": N, "tools": [...]}Motivation
Pipes like this used to need manual text munging and two-step parsing:
Now:
Test plan
go build ./...go vet ./...go test ./cmd/...(4 new tests cover unwrap, isError, passthrough, error envelope){"ok": false, "error": "..."}and exit 1