Skip to content

fix(docs): rename stale gittensory reference in miner MCP client-config doc #5957

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

Merged
JSONbored merged 1 commit into from
Jul 15, 2026
Merged

fix(docs): rename stale gittensory reference in miner MCP client-config doc #5957

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions packages/loopover-miner/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,7 +264,7 @@ This completes the read-only AMS MCP tool surface (status, portfolio, claims, ev
```json
{
"mcpServers": {
"gittensory": {
"loopover": {
"command": "loopover-mcp",
"args": ["--stdio"]
},
Expand All @@ -276,7 +276,7 @@ This completes the read-only AMS MCP tool surface (status, portfolio, claims, ev
}
```

`gittensory` exposes ORB's hosted contributor-workflow tools (issue ranking, PR packet prep, decision packs). `loopover-miner` exposes AMS's own local state-visibility tools listed above (portfolio dashboard, claims, audit feed, run state, plans) — a fully separate, 100% local tool surface with no shared code or network calls between the two. Both follow the same `loopover_*` tool-naming convention (`loopover_...` vs. `loopover_miner_...`), but back onto different stores: ORB's tools read the hosted gittensory backend, AMS's tools read this machine's own local SQLite files (see [Local storage](#local-storage)) — a handful of AMS tools even name the ORB tool they mirror (e.g. `loopover_miner_get_run_state` is the read-only analog of `loopover_get_automation_state`) so the relationship is explicit at the point of use, not just here.
`loopover` exposes ORB's hosted contributor-workflow tools (issue ranking, PR packet prep, decision packs). `loopover-miner` exposes AMS's own local state-visibility tools listed above (portfolio dashboard, claims, audit feed, run state, plans) — a fully separate, 100% local tool surface with no shared code or network calls between the two. Both follow the same `loopover_*` tool-naming convention (`loopover_...` vs. `loopover_miner_...`), but back onto different stores: ORB's tools read the hosted loopover backend, AMS's tools read this machine's own local SQLite files (see [Local storage](#local-storage)) — a handful of AMS tools even name the ORB tool they mirror (e.g. `loopover_miner_get_run_state` is the read-only analog of `loopover_get_automation_state`) so the relationship is explicit at the point of use, not just here.

## Version check

Expand Down
4 changes: 2 additions & 2 deletions test/unit/miner-mcp-client-config-doc.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ describe("miner MCP client config example (#5163)", () => {
const readme = readFileSync(README_PATH, "utf8");
const config = JSON.parse(extractFirstJsonBlock(readme));

expect(config.mcpServers.gittensory).toEqual({
expect(config.mcpServers.loopover).toEqual({
command: "loopover-mcp",
args: ["--stdio"],
});
Expand All @@ -39,7 +39,7 @@ describe("miner MCP client config example (#5163)", () => {

it("cross-references the ORB MCP README's own Client config section", () => {
const readme = readFileSync(README_PATH, "utf8");
expect(readme).toContain("../gittensory-mcp/README.md#client-config");
expect(readme).toContain("../loopover-mcp/README.md#client-config");

const mcpReadme = readFileSync(MCP_README_PATH, "utf8");
expect(mcpReadme).toContain("### Client config");
Expand Down