Context
Today there's no documented way to run both the hosted @jsonbored/gittensory-mcp stdio server and the new AMS-side gittensory-miner mcp stdio server (introduced by the MCP scaffold issue in this batch) together in a single MCP-capable client session (Claude Desktop / Claude Code). packages/gittensory-miner/README.md has no MCP client config example today, leaving a documentation gap between ORB's contributor-workflow tools and AMS's own state-visibility tools.
Dependencies
Requires the MCP scaffold issue in this same batch ("Scaffold a minimal gittensory-miner mcp stdio server") to land first, since the gittensory-miner mcp bin entry this example registers doesn't exist until that PR merges. Should ideally land after at least one or two of the read-only AMS tool PRs (portfolio dashboard, claims, event-ledger, etc.) so the example config isn't describing an empty/no-op tool surface, but is not strictly blocked on all of them landing.
Requirements
- Add a documented example (in packages/gittensory-miner/README.md or a new docs/mcp-setup.md) showing a Claude Desktop / Claude Code style JSON MCP client config.
- The example must register two separate MCP servers:
npx @jsonbored/gittensory-mcp --stdio (the existing hosted ORB tools) and the new gittensory-miner mcp bin entry (AMS's own tools).
- Include a short explanation of what each server exposes (ORB's contributor-workflow tools vs. AMS's state-visibility tools) so a reader understands why both are useful together.
- Cross-reference this example from the package README's MCP documentation section (added by the "document the new tool surface" issue in this batch) so a reader lands on it naturally.
- Do not introduce any new code, scripts, or runtime behavior — this is a documentation-only addition.
Deliverables / Acceptance Criteria
Test Coverage Requirements
This PR must ship with full test coverage for every changed line and branch — the repo's Codecov patch gate requires 99%+ coverage and the house standard is to aim for 100%, including both sides of every conditional/nullish-coalescing branch introduced. Since this is a documentation-only change touching no src/** logic, there is no new executable code under Codecov's patch gate. Add: (1) N/A — no unit tests apply since no runtime code changes, (2) a lightweight invariant check that the example JSON snippet is syntactically valid JSON (e.g. a simple parse assertion in a doc-lint step, if the repo's doc tooling supports it), and (3) N/A — not a bug fix, no regression test needed.
Expected Outcome
A contributor running AMS locally can copy one JSON snippet into their MCP client config and immediately have both ORB's and AMS's MCP tool surfaces available in the same session, without guessing at bin-entry names or server registration syntax.
Links & Resources
- packages/gittensory-miner/README.md
- Possible new file: docs/mcp-setup.md
- See the MCP scaffold issue in this same batch (bin entry:
gittensory-miner mcp)
- See the "document the new tool surface" issue in this same batch
- Theme: MCP exposure
Context
Today there's no documented way to run both the hosted
@jsonbored/gittensory-mcpstdio server and the new AMS-sidegittensory-miner mcpstdio server (introduced by the MCP scaffold issue in this batch) together in a single MCP-capable client session (Claude Desktop / Claude Code). packages/gittensory-miner/README.md has no MCP client config example today, leaving a documentation gap between ORB's contributor-workflow tools and AMS's own state-visibility tools.Dependencies
Requires the MCP scaffold issue in this same batch ("Scaffold a minimal
gittensory-miner mcpstdio server") to land first, since thegittensory-miner mcpbin entry this example registers doesn't exist until that PR merges. Should ideally land after at least one or two of the read-only AMS tool PRs (portfolio dashboard, claims, event-ledger, etc.) so the example config isn't describing an empty/no-op tool surface, but is not strictly blocked on all of them landing.Requirements
npx @jsonbored/gittensory-mcp --stdio(the existing hosted ORB tools) and the newgittensory-miner mcpbin entry (AMS's own tools).Deliverables / Acceptance Criteria
Test Coverage Requirements
This PR must ship with full test coverage for every changed line and branch — the repo's Codecov patch gate requires 99%+ coverage and the house standard is to aim for 100%, including both sides of every conditional/nullish-coalescing branch introduced. Since this is a documentation-only change touching no
src/**logic, there is no new executable code under Codecov's patch gate. Add: (1) N/A — no unit tests apply since no runtime code changes, (2) a lightweight invariant check that the example JSON snippet is syntactically valid JSON (e.g. a simple parse assertion in a doc-lint step, if the repo's doc tooling supports it), and (3) N/A — not a bug fix, no regression test needed.Expected Outcome
A contributor running AMS locally can copy one JSON snippet into their MCP client config and immediately have both ORB's and AMS's MCP tool surfaces available in the same session, without guessing at bin-entry names or server registration syntax.
Links & Resources
gittensory-miner mcp)