Repository navigation
feat: dynamic command generation from MCP tools/list - #5
Merged
Merged
Conversation
Auto-generate CLI commands from cached MCP tool definitions so every Pipeboard tool is available as `pipeboard <platform> <command> --flags`. - `pipeboard refresh` fetches tools from all MCP servers and caches to ~/.pipeboard/tools-cache.json - On startup, loads cache and registers Cobra subcommands per platform (google-ads, meta-ads) with per-tool subcommands - Tool name mapping: strips platform prefix, converts to kebab-case (e.g. get_google_ads_campaigns → get-campaigns) - JSON Schema inputSchema → typed CLI flags with descriptions, enum hints, and required enforcement - MCP text content is extracted and pretty-printed as JSON
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
1 participant
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
pipeboard refreshcommand that fetches tool definitions from all Pipeboard MCP servers (google-ads-mcp, meta-ads-mcp) and caches them locally at~/.pipeboard/tools-cache.jsonpipeboard google-ads <tool>andpipeboard meta-ads <tool>with typed flags derived from each tool JSON Schemaget_google_ads_campaigns->pipeboard google-ads get-campaigns), required flags are enforced, and enum values are shown in help textTest plan
make build && make test && make lintpasspipeboard refreshwith valid auth token populates cachepipeboard google-ads --helplists all generated subcommandspipeboard google-ads get-campaigns --customer-id <id>calls the MCP server and returns formatted JSON