Repository navigation
v1.2.0
Added
-
status --jsonprints the same state as one JSON object on stdout, so
a script can read whether this server is authorised instead of parsing
the text written for a person.credentials.resolvedis the field to
branch on;schema_versionchanges only when a field is removed or its
meaning changes, never when one is added.The design is an outside contributor's, taken from the Drive server
where it landed first, and the reason is a fault this repository has
already caused: a label moved under a release —refresh token:became
token store:— and a check written against the old one started
reading "not authorised" for an account that was fine. It fails
silently, and the usual response to "not authorised" is to runlogin,
which asks a person for consent they already gave.One collector, two renderers, so the two cannot drift: the text output
is byte-identical to what the released binary prints, which is asserted
by diffing them rather than by reading.The account is masked at the collector, not on the way out. The
text path redacts insideoutf; the JSON encoder does not go through
it, so a struct written straight to the stream would have carried the
address in full. Held by a test that drives the collector and was
watched failing with the redaction removed.
Built by GoReleaser from the tag. Every archive carries the binary,
LICENSE and README, and ships an SBOM beside it.
Verify a download before you run it:
sha256sum -c checksums.txt --ignore-missing
cosign verify-blob checksums.txt --bundle checksums.txt.bundle \
--certificate-identity-regexp 'https://github\.com/mmedum/google-docs-mcp/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
gh attestation verify google-docs-mcp_*.tar.gz --repo mmedum/google-docs-mcp