@qmediat.io/gemini-code-context-mcp 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +20 -0
- package/README.md +10 -8
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [1.0.1] — 2026-04-19
|
|
11
|
+
|
|
12
|
+
Docs-only patch. No behavioural changes. Triggered by user spotting an inaccurate claim about the incumbent `jamubc/gemini-mcp-tool` in the README comparison table.
|
|
13
|
+
|
|
14
|
+
### Fixed
|
|
15
|
+
|
|
16
|
+
After empirical verification against both the published npm v1.1.4 tarball AND the project's `main` branch on GitHub, four comparison-table claims were corrected. All structural points (hardcoded default, no caching, CLI backend, unreleased improvements) still hold; wording was imprecise.
|
|
17
|
+
|
|
18
|
+
- **Default model** — was stated as hardcoded `gemini-3.1-pro-preview`. That's true of npm v1.1.4, but on GitHub `main` (which is what anyone browsing the repo sees — last commit 2025-07-23) the hardcoded value is `gemini-2.5-pro`. Table now anchors to `main` and a footnote calls out the npm-vs-main drift.
|
|
19
|
+
- **Repeat queries** — "Re-sends entire codebase every call" was misleading; jamubc doesn't auto-index the workspace. Users control what's sent via `@file` syntax. The accurate delta is **no caching layer**: each call re-tokenises referenced files regardless of whether they've been tokenised before.
|
|
20
|
+
- **Auth** — "Key in `~/.claude.json` env var" was wrong for typical jamubc setups. The server inherits the `gemini` CLI's own auth — browser OAuth via `gemini auth login`, or `GEMINI_API_KEY` env var.
|
|
21
|
+
- **Dead deps** — numerical correction. On GitHub `main` the unused-in-src deps are five (`ai`, `chalk`, `d3-shape`, `inquirer`, `prismjs`). In the shipped npm `v1.1.4` tarball only three (`ai`, `d3-shape`, `prismjs`) are unused — `chalk` and `inquirer` are imported in `dist/` for that version. Table anchors to `main`; footnote acknowledges the npm-side count.
|
|
22
|
+
- Added table footnote explaining that all comparisons reference jamubc on GitHub `main` and acknowledging the ~9-month drift between that and the published npm version.
|
|
23
|
+
|
|
24
|
+
Same corrections applied in `docs/migration-from-jamubc.md`.
|
|
25
|
+
|
|
26
|
+
### Why this matters
|
|
27
|
+
|
|
28
|
+
The v1.0.0 README was the first public artefact advertising the project on npm. Claims about a competing project must be defensible line-by-line. One reader's spot-check caught the drift, which triggered a full empirical audit of the table. The corrections don't change our value proposition — they just describe the incumbent accurately.
|
|
29
|
+
|
|
10
30
|
## [1.0.0] — 2026-04-19
|
|
11
31
|
|
|
12
32
|
First public release. An MCP server that wraps Google's Gemini API with persistent Context Caching so Claude Code (and other MCP hosts) can query large codebases with cached input tokens instead of re-sending the entire workspace on every prompt.
|
package/README.md
CHANGED
|
@@ -16,14 +16,16 @@ An MCP (Model Context Protocol) server that wraps Google's Gemini API with **per
|
|
|
16
16
|
|
|
17
17
|
| | [jamubc/gemini-mcp-tool](https://github.com/jamubc/gemini-mcp-tool) | **`@qmediat.io/gemini-code-context-mcp`** |
|
|
18
18
|
|---|---|---|
|
|
19
|
-
| Maintenance | Abandoned (last release 2025-07) |Actively maintained |
|
|
20
|
-
| Default model | Hardcoded `gemini-
|
|
21
|
-
| Backend | Shells out to `gemini` CLI (
|
|
22
|
-
| Repeat queries |
|
|
23
|
-
| Coding delegation |
|
|
24
|
-
| Auth |
|
|
25
|
-
| Cost control | — |Daily budget cap in USD (`GEMINI_DAILY_BUDGET_USD`) |
|
|
26
|
-
| Dead deps | 5 unused packages (`ai`, `chalk`, `d3-shape`,
|
|
19
|
+
| Maintenance | Abandoned (last release 2025-07) | Actively maintained |
|
|
20
|
+
| Default model | Hardcoded `gemini-2.5-pro` (main) — no runtime override | Dynamic `latest-pro` alias — resolves against your API key tier at startup |
|
|
21
|
+
| Backend | Shells out to `gemini` CLI (subprocess per call) | Direct `@google/genai` SDK |
|
|
22
|
+
| Repeat queries | No caching layer — each call re-tokenises referenced files | **Files API + Context Cache** — repeat queries reuse the indexed codebase; cached input tokens billed at ~25 % of the uncached rate |
|
|
23
|
+
| Coding delegation | Prompt-injection `changeMode` (OLD/NEW format in system text) | Native `thinkingConfig` + optional `codeExecution` |
|
|
24
|
+
| Auth | Inherits `gemini` CLI auth (browser OAuth via `gemini auth login`, or env var) | 3-tier: Vertex ADC / credentials file (chmod 0600 atomic write) / env var (+ warning) |
|
|
25
|
+
| Cost control | — | Daily budget cap in USD (`GEMINI_DAILY_BUDGET_USD`) |
|
|
26
|
+
| Dead deps | 5 unused packages (`ai`, `chalk`, `d3-shape`, `inquirer`, `prismjs`) | Zero dead deps |
|
|
27
|
+
|
|
28
|
+
> *Comparison points reference `jamubc/gemini-mcp-tool` as seen on its GitHub `main` branch (most current snapshot, last commit 2025-07-23). The published npm v1.1.4 is ~9 months older and differs in a few specifics — default model is `gemini-3.1-pro-preview` there instead of `gemini-2.5-pro`, and only 3 of the 5 deps are dead in that tarball (`chalk` and `inquirer` still imported). The structural claims (hardcoded model, no caching, `gemini` CLI backend, unreleased improvements stuck behind an abandoned npm registry entry) hold for both.*
|
|
27
29
|
|
|
28
30
|
## Quick start
|
|
29
31
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@qmediat.io/gemini-code-context-mcp",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"description": "MCP server that gives Claude Code persistent memory of your codebase, backed by Gemini's 2M-token context. Drop-in upgrade over the abandoned gemini-mcp-tool.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"mcp",
|