This release is a pre-release and may not be stable for production use.
node-wire-google-drive
Google Drive connector for Node Wire. Lets an agent or app list, read, create, upload, update and delete files in Google Drive (API v3) and share them with other users. It authenticates as a service account, or with each caller's own Google token.
Part of Node Wire. Every call runs through the Node Wire runtime, so it gets input validation, retries with a circuit breaker, scope policy, a shared error taxonomy, and OpenTelemetry tracing. A Node Wire host exposes each action over REST, gRPC and MCP.
Install
pip install node-wire-google-drive
This pulls in node-wire-runtime. Pre-releases
are published as X.Y.ZbN; install one with pip install --pre node-wire-google-drive. To install
every connector at once, use node-wire-connectors.
Wheels are compiled with Cython and contain no Python source. They are built for CPython 3.11, 3.12 and 3.13 on Linux x86_64 (manylinux and musllinux), macOS arm64 and Windows x64.
Actions
The connector registers as google_drive. MCP tool names are <connector_id>_<action>, with
dots replaced by underscores.
| Action | MCP tool | What it does |
|---|---|---|
files.list |
google_drive_files_list |
Lists or searches files, with an optional Drive query and fields mask |
files.get |
google_drive_files_get |
Fetches the metadata of one file |
files.create |
google_drive_files_create |
Creates a file or folder entry (metadata only), optionally inside a folder |
files.upload |
google_drive_files_upload |
Creates a new file with text content |
files.update |
google_drive_files_update |
Updates a file's metadata or moves it between folders |
files.delete |
google_drive_files_delete |
Deletes a file |
permissions.create |
google_drive_permissions_create |
Shares a file with a user as reader, commenter, writer or owner |
Configuration
Add the connector to config/connectors.yaml:
connectors:
google_drive:
enabled: true
exposed_via: ["rest", "grpc", "mcp"]
auth:
provider: service_account
sa_json_secret: GOOGLE_DRIVE_SA_JSON
scopes:
- https://www.googleapis.com/auth/drive
Secrets are read through the configured secret provider (environment variables by default):
| Variable | Purpose |
|---|---|
GOOGLE_DRIVE_SA_JSON |
Service-account key: the JSON contents, or (locally) an absolute path to the key file |
Per-user access (upstream_bearer)
Instead of a service account, the connector can forward each caller's own Google access token, so every call runs with that user's Drive permissions. This is a trust-boundary decision: Node Wire forwards the token as-is and does not check that it was issued for Drive. It is enabled only when both of these are set, and fails closed otherwise:
auth: { provider: upstream_bearer }inconfig/connectors.yaml(orGOOGLE_DRIVE_AUTH_PROVIDER=upstream_bearer)NW_UPSTREAM_BEARER_CONNECTORS=google_drive
Usage
Set NW_ALLOWED_CONNECTORS=google_drive (comma-separate several). Node Wire loads only the
connectors listed there, and discovers them through the node_wire.connectors entry point.
A Node Wire host (the REST, gRPC or MCP server, or ConnectorFactory) then builds the connector
from the configuration above. See Use a connector.
Documentation
- Node Wire on GitHub: source, issues and full documentation
- Google Drive setup guide: service-account setup, per-user access and error codes
- Connector reference
- Configuration
- Error codes
- Changelog
License
Apache-2.0. See LICENSE.
Metadata
Release files for node-wire-google-drive 1.0.0b1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 7.5 MB
Release files / node_wire_google_drive-1.0.0b1-cp313-cp313-win_amd64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 164.2 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9033c3973384d774cdb9a8d7d54b56b7ea536f756a177ff31da5608ee97fc9f0
|
|
BLAKE2b-256 checksum How to use checksums |
4780799cdffbfce4f5737d472e4ec802cad242fcef9a095cc145b37c110da8d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
d7cfc9900850620f2cf7ce25b132e374b7ce9b6934bb371b21ebfb9935fab818
|
|
BLAKE2b-256 checksum How to use checksums |
a5a48f7278c706068a763014f7f8d09c52ea3e2adecf4e9560c62c985183d738
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0055a90483fa604ab51f95d7b80dda7ceb758fbf9f0793d00647a19313231bd6
|
|
BLAKE2b-256 checksum How to use checksums |
b6ec74ec2e896390dd900f1eb1bc2502f9d882e066102eb16738f4341ee71d32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 181.7 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c61a9d23318d7f8cde0b5bb801b76db32e57dda8116df7e4f1b454dbd818211e
|
|
BLAKE2b-256 checksum How to use checksums |
92d8570a3ada2f7bd9ff35cd5cce0385ac34320ceefee7c5bfd9450af3937a99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp312-cp312-win_amd64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 167.7 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6037a60156c4788ba6522e3553327fbf891f0ac70698595e6df624cdb0417916
|
|
BLAKE2b-256 checksum How to use checksums |
4cb645e16b16f90e600961a1d6b3e380a5f6309bc94a525048fa62e80780c960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
ca81b001f184b2582409a8962eed1911183095e1285a63b917e41ee4824b6d5a
|
|
BLAKE2b-256 checksum How to use checksums |
e82aa35b42b5f6436b0c5c9ff7451f7a126e5923952756c11b28684cef0d4698
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
7eb19cbe76db2b8f2fcb5fb421a700d3ca59c1378906f9c55c7588eba83c5906
|
|
BLAKE2b-256 checksum How to use checksums |
de62faed9afa3d6dc86d11294398bb44a7490d860739b11caad5a5c9c603aca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 185.6 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c78ef70d9ee6c5f0accebbf112827cda154074e336030ed9f8cafbd79039bddf
|
|
BLAKE2b-256 checksum How to use checksums |
8a3c8f2dde976802a24612dbbf5c7e813ddfeeeb5d94a0dc260e73f9a3e4db00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp311-cp311-win_amd64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 175.8 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
2f0bc25ca963a99c95d5b0e8061ed7fe4959dc0b0238d185f8d05a8c6676ef20
|
|
BLAKE2b-256 checksum How to use checksums |
596469560f2da401dcccb121d613612d708f6f09608be39b7b016ea1970b805e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
b2eeac15e82b3482be9f186f015f5621e50cd2624a366b6535172324e4af1698
|
|
BLAKE2b-256 checksum How to use checksums |
989ba0f54a4676cdd21fbb45edb825a3ea368960c591c754e6a728165438da1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
3013bc806241d44c7e1e9ae49eebcee426c1b453fabbfe340f3b0f6180f4ce93
|
|
BLAKE2b-256 checksum How to use checksums |
afc124d870f52b3372c12b7c04f22f0df87377911b95ab45e164e5984c45dbfa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / node_wire_google_drive-1.0.0b1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | node_wire_google_drive-1.0.0b1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 182.6 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
b803d8c9e081a7abf204e58788c5d6cf3add14f5ac17541cb8afe69aeac24b5e
|
|
BLAKE2b-256 checksum How to use checksums |
3d4225c56aa0f7b98cf00dc59a721b9cdd3bc58e890182d26c4887b7c639de70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency log
