## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Paperclip runs across the CLI, server, adapters, plugins, CI, and container images. > - These surfaces declared different Node.js versions from 20 through 24. > - A newer `@types/node` major can expose APIs that the supported runtime does not provide. > - Node.js 20 is no longer a suitable project baseline, and Node.js 24 is the current LTS line. > - This pull request sets Node.js 24.11.0 as one repository-wide baseline, adds a drift check, and gives users actionable startup guidance when their runtime is too old. > - The benefit is one clear runtime contract for development, release, installation, and published packages. ## Linked Issues or Issue Description Refs #2734 Refs #11727 Refs #739 ## What Changed - Require Node.js 24.11.0 or newer in all 42 package manifests and runtime checks. - Use Node.js 24 in GitHub Actions, Docker images, smoke images, sandbox setup, portable installs, and esbuild targets. - Align every direct `@types/node` declaration on `^24.0.0`. - Prevent Dependabot from opening major `@types/node` upgrades without a matching runtime decision. - Add `.nvmrc` and a CI policy check for Node version drift. - Update ACP version gates, tests, and user documentation for the new minimum. - Print a non-blocking warning on CLI and server startup when Node is unsupported, with remediation through a version manager or the documented downloaded `install.sh` workflow. - Deduplicate that warning when `paperclipai run` boots the CLI and server in the same process. ## Verification - `node scripts/check-node-version-policy.mjs` - `node --check scripts/check-node-version-policy.mjs` - `node --check cli/esbuild.config.mjs` - `node --check scripts/generate-npm-package-json.mjs` - `bash -n scripts/install.sh scripts/test-install-sh-docker.sh scripts/e2e-install-lifecycle.sh` - Parsed all 42 package manifests and confirmed `engines.node` is `>=24.11.0`. - `git diff --check` - `vitest run packages/adapter-utils/src/sandbox-install-command.test.ts` passed with 3 tests. - `vitest run cli/src/node-version.test.ts` passed with 4 tests. - Directly exercised the shared warning helper for unsupported-version messaging and same-process deduplication. - The focused exe.dev suite could not resolve the locally unbuilt plugin SDK from this isolated worktree. A full offline workspace install was also blocked because the package-manager signature verifier requires registry access. The full suite was not run locally; draft CI performs a clean install and evaluates the wider impact. ## Risks - This is a breaking runtime change for users, plugins, and deployments that still use Node.js 20 or 22. - Published workspace packages will now produce an engine warning or failure in strict package managers on older Node.js releases. - Node.js 24 can reveal dependency, native module, Playwright, or agent CLI compatibility issues in CI. - The bootstrap installer now installs Node.js 24 when the current runtime is older than 24.11.0. - The portable sandbox fallback is pinned to Node.js 24.11.0 and depends on that upstream tarball remaining available. - Unsupported runtimes continue booting after a warning, so a later incompatibility can still fail at its point of use. - The CLI and server share the warning policy through the published `@paperclipai/shared` package; packaging checks must keep that subpath export available. - This PR does not commit `pnpm-lock.yaml` because repository policy assigns lockfile generation to CI. > For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and discuss it in `#dev` before opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. See `CONTRIBUTING.md`. ## Model Used - OpenAI Codex based on GPT-5. The exact deployment ID and context window are not exposed in this session. Reasoning, repository tools, shell execution, and GitHub tools were enabled. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [x] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [x] All Paperclip CI gates are green - [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| src | ||
| README.md | ||
| package.json | ||
| tsconfig.json | ||
| vitest.config.ts | ||
README.md
Google Sheets MCP Server
First-party MCP server for Google Sheets API v4. It can run as a Paperclip
local_stdio gallery connection or as a local Streamable HTTP server for
Paperclip's remote_http connect-by-link flow.
Configuration
The server uses Google service-account credentials only. OAuth is intentionally not supported in v1.
Required:
GOOGLE_SHEETS_ALLOWED_SPREADSHEET_IDS: comma or newline separated spreadsheet IDs the server may access.- One of:
GOOGLE_SHEETS_SERVICE_ACCOUNT_JSON: inline service-account JSON, or a path to a service-account JSON file.GOOGLE_SHEETS_SERVICE_ACCOUNT_JSON_PATH: path to a service-account JSON file.
Equivalent CLI flags are available for local stdio templates:
paperclip-google-sheets-mcp-server \
--service-account-json-path /path/to/service-account.json \
--allowed-spreadsheet-ids sheet_id_1,sheet_id_2
Share each allowed spreadsheet with the service account's client_email.
Paperclip local_stdio Test Path
Use the Google Sheets gallery app when you want Paperclip to supervise the server as a stdio MCP process:
- Configure Paperclip's Google Sheets service account environment so the
gallery marks Google Sheets as available. The service account JSON must be
provided by
GOOGLE_SHEETS_SERVICE_ACCOUNT_JSONorGOOGLE_SHEETS_SERVICE_ACCOUNT_JSON_PATH. - Share every spreadsheet you want to test with the service account's
client_email. - In Paperclip, open the tool app gallery, choose Google Sheets, and paste one or more Google Sheets links.
- Save the app connection. Paperclip creates a
local_stdioconnection using thepaperclip.google-sheetstemplate and passes the selected spreadsheet IDs to this server asGOOGLE_SHEETS_ALLOWED_SPREADSHEET_IDS. - Refresh the tool catalog and verify the Google Sheets tools appear for the connection.
In this path, the spreadsheet allowlist comes from the gallery wizard. Every tool call is still checked against the server-side allowlist before the server calls Google.
Paperclip remote_http Test Path
Use the HTTP binary when you want to exercise the same tools through
Paperclip's remote_http gateway:
GOOGLE_SHEETS_SERVICE_ACCOUNT_JSON_PATH=/path/to/service-account.json \
GOOGLE_SHEETS_ALLOWED_SPREADSHEET_IDS=sheet_id_1,sheet_id_2 \
GOOGLE_SHEETS_MCP_HOST=127.0.0.1 \
GOOGLE_SHEETS_MCP_PORT=8849 \
GOOGLE_SHEETS_MCP_TOKEN=local-test-token \
paperclip-google-sheets-mcp-http-server
The HTTP server prints the MCP endpoint on startup. With the values above, use:
http://127.0.0.1:8849/mcp
Then in Paperclip, choose the remote HTTP or "connect with a link" path, paste
the /mcp URL, and configure the bearer token if GOOGLE_SHEETS_MCP_TOKEN is
set. The HTTP server accepts the token only as an Authorization: Bearer <token> header.
HTTP configuration:
GOOGLE_SHEETS_MCP_HOST: host to bind. Defaults to127.0.0.1. If this is not a loopback host,GOOGLE_SHEETS_MCP_TOKENis required and startup fails closed when the token is omitted.GOOGLE_SHEETS_MCP_PORT: port to bind. Defaults to8849.PORT: platform-style port override. When set, it takes precedence overGOOGLE_SHEETS_MCP_PORT.GOOGLE_SHEETS_MCP_TOKEN: optional shared secret for the/mcproute. Omit only for loopback/local single-operator testing where no other process can reach the server.
The HTTP server reuses the same service-account and spreadsheet allowlist
environment as stdio. In this phase, the HTTP spreadsheet allowlist is
process-level configuration (GOOGLE_SHEETS_ALLOWED_SPREADSHEET_IDS or
GOOGLE_SHEETS_SPREADSHEET_IDS), not a per-connection Paperclip gallery wizard
setting or shared multi-tenant policy. Treat this as a local/single-operator
test path. Restart the HTTP process with a different allowlist when you need to
test a different spreadsheet set.
Tools
list_spreadsheets(read)get_spreadsheet_info(read)read_values(read)search_rows(read)append_rows(write)update_values(write)add_sheet_tab(write)clear_values(destructive)delete_rows(destructive)
Every tool that accepts a spreadsheet ID rejects IDs outside the configured
allowlist before calling Google. list_spreadsheets lists only the allowlisted
IDs.