Skip to content

feat(mcp-cli): add tools command listing stdio tool descriptors - #4222

Closed
jsdevninja wants to merge 1 commit into
JSONbored:mainfrom
jsdevninja:feat/mcp-cli-tools-command
Closed

feat(mcp-cli): add tools command listing stdio tool descriptors#4222
jsdevninja wants to merge 1 commit into
JSONbored:mainfrom
jsdevninja:feat/mcp-cli-tools-command

Conversation

@jsdevninja

@jsdevninja jsdevninja commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add gittensory-mcp tools [--json] so contributors can list every local stdio MCP tool name + one-line description without starting --stdio and speaking MCP.
  • Refactor stdio tool descriptors into STDIO_TOOL_DESCRIPTORS as the single source of truth used by both server.registerTool and the new command (behavior unchanged).
  • Wire tools into CLI_COMMAND_SPEC (shell completion), printHelp(), and the package README; assert CLI tool count/descriptions match the live registered stdio tools.

Closes #2233.

Scope

  • The PR title follows type(scope): short summary Conventional Commit format, for example fix(api): restore profile access checks.
  • This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
  • This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
  • I linked a currently open issue this PR resolves (e.g. Closes #123) — a linked open issue is required for every contributor PR.

Validation

  • git diff --check
  • npm run actionlint
  • npm run typecheck
  • npm run test:coverage locally; codecov/patch requires ≥99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.
  • npm run test:workers
  • npm run build:mcp
  • npm run test:mcp-pack
  • npm run ui:openapi:check
  • npm run ui:lint
  • npm run ui:typecheck
  • npm run ui:build
  • npm audit --audit-level=moderate
  • New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:

  • MCP-package-only change under packages/gittensory-mcp/** + test/unit/mcp-cli-*.test.ts (Codecov ignores packages/** and test/**). Ran focused MCP CLI tests (mcp-cli-tools, mcp-cli-basics, related stdio discovery/proxy suites) and npm run build:mcp. Remaining full-gate jobs left to CI path filters / validate.

Safety

  • No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
  • Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
  • Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests.
  • API/OpenAPI/MCP behavior is updated and tested where needed.
  • UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
  • Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.
  • Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

UI Evidence

N/A — CLI/MCP packaging change only; no visible UI.

Notes

@jsdevninja
jsdevninja requested a review from JSONbored as a code owner July 8, 2026 15:07
@superagent-security

Copy link
Copy Markdown
Contributor

Superagent didn't find any vulnerabilities or security issues in this PR.

@codecov

codecov Bot commented Jul 8, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.76%. Comparing base (f53d4e5) to head (a1d7758).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4222   +/-   ##
=======================================
  Coverage   93.76%   93.76%           
=======================================
  Files         390      390           
  Lines       36553    36553           
  Branches    13389    13389           
=======================================
  Hits        34274    34274           
  Misses       1623     1623           
  Partials      656      656           
🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@loopover-orb loopover-orb Bot added the gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier. label Jul 8, 2026
@loopover-orb

loopover-orb Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Important

🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪

🔍 Gittensory is reviewing…

AI analysis is in progress. This comment will update when the review is complete.

🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟪 Reviewing

@jsdevninja
jsdevninja marked this pull request as draft July 8, 2026 15:18
@loopover-orb loopover-orb Bot closed this Jul 8, 2026
@loopover-orb

loopover-orb Bot commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Gittensory had already started reviewing this pull request — converting it to draft to dodge the one-shot review process is not allowed. Please open a new pull request with the issues addressed.

@loopover-orb loopover-orb Bot added the review-evasion Gittensor contributor context label Jul 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier. review-evasion Gittensor contributor context

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(mcp-cli): add a gittensory-mcp tools command that lists every stdio tool + description

1 participant