Skip to content

feat: add placeholder list-tools CLI command (PoC) #618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add placeholder list-tools CLI command (PoC) #618

wants to merge 1 commit into from
+105 −0

Conversation

salignatmoandal
Copy link

What does this PR do?

Adds a minimal list-tools CLI command to the GitHub MCP Server.
This is a proof of concept to evaluate whether a tool discovery feature is useful before committing to full implementation.

Why is this useful?

•	Quick discovery of available tools (without digging through documentation)
•	Helps debug server configuration (active toolsets, read-only mode, etc.)
•	Offers a human-readable snapshot of server capabilities
•	Can assist tooling developers (Cursor, Copilot, Claude) in surfacing MCP capabilities

Current Behavior

Running the following:

go run cmd/github-mcp-server/main.go list-tools

Outputs:

TODO: Implement list-tools functionality
This is a proof of concept for the list-tools command.
Would display all available MCP tools grouped by toolset.

Implementation (Minimal for Now)

•	Adds a new CLI command via Cobra (list-tools)
•	Only placeholder logic for now
•	Prints a TODO message to validate the concept
•	No impact on existing behavior

Proposed Next Steps (if validated)

•	Group tools by toolset and print names/descriptions
•	Add flags:
•	--toolset=<name> to filter
•	--format=json|yaml|table
•	Respect --read-only, --toolsets, and dynamic toolset modes
•	Add tests and documentation

Question

Would this feature be useful to others?
If yes, I’d be happy to expand this into a fully usable command.

@salignatmoandal salignatmoandal requested a review from a team as a code owner June 30, 2025 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@salignatmoandal