Add the same gittensory_find_opportunities tool to the packages/gittensory-mcp stdio CLI (bin/gittensory-mcp.js), so a contributor using the published npm package gets the identical cross-repo discovery capability without needing the hosted Worker. Mirrors the existing proxy pattern already used for gittensory_check_before_start in the same file (an apiPost/apiGet call against the hosted API), so the CLI stays a thin, versioned wrapper rather than reimplementing the ranking logic client-side.
Deliverables
References
packages/gittensory-mcp/bin/gittensory-mcp.js line ~363 (gittensory_check_before_start registration + its apiPost proxy call) — the exact pattern to mirror for the new tool
test/unit/mcp-discovery.test.ts — the existing stdio-client-connect test pattern (spawns bin/gittensory-mcp.js via StdioClientTransport)
- the companion hosted-tool issue (
feat(mcp): add gittensory_find_opportunities tool to the hosted /mcp Worker) — defines the exact input/output schema this CLI proxy must match byte-for-byte
Add the same
gittensory_find_opportunitiestool to thepackages/gittensory-mcpstdio CLI (bin/gittensory-mcp.js), so a contributor using the published npm package gets the identical cross-repo discovery capability without needing the hosted Worker. Mirrors the existing proxy pattern already used forgittensory_check_before_startin the same file (anapiPost/apiGetcall against the hosted API), so the CLI stays a thin, versioned wrapper rather than reimplementing the ranking logic client-side.Deliverables
gittensory_find_opportunitiesinpackages/gittensory-mcp/bin/gittensory-mcp.jsviaserver.registerTool(...), following the exact shape of the neighboringgittensory_check_before_startregistration (same file, ~line 363): sameinputSchemafields as the hosted tool, proxying to a new/v1/opportunities/find(or equivalent) endpoint via the file's existingapiPosthelper.packageVersion/compatibilityPathversion-negotiation guard (already present at the top ofbin/gittensory-mcp.js) covers this new tool the same way it covers every existing proxied tool — i.e. no special-casing needed, just confirm via a test that an old CLI talking to a newer API degrades gracefully.test/unit/mcp-discovery.test.ts's stdio-connect pattern) spawning the actual CLI binary viaStdioClientTransport, callinggittensory_find_opportunities, and asserting the response shape matches the hosted tool's output schema.packages/gittensory-mcp/README.md's tool list/table (if one exists) to include the new tool, matching how every other tool is documented there.References
packages/gittensory-mcp/bin/gittensory-mcp.jsline ~363 (gittensory_check_before_startregistration + itsapiPostproxy call) — the exact pattern to mirror for the new tooltest/unit/mcp-discovery.test.ts— the existing stdio-client-connect test pattern (spawnsbin/gittensory-mcp.jsviaStdioClientTransport)feat(mcp): add gittensory_find_opportunities tool to the hosted /mcp Worker) — defines the exact input/output schema this CLI proxy must match byte-for-byte