@cocal/google-calendar-mcp
It exited or refused to answer until it is given configuration, such as a key or an argument. Run 2026-11-16.
Needs to start: GOOGLE_OAUTH_CREDENTIALS, GOOGLE_CALENDAR_MCP_TOKEN_PATH
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @cocal/google-calendar-mcp@2.8.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Its error output names these settings: GOOGLE_OAUTH_CREDENTIALS, GOOGLE_CALENDAR_MCP_TOKEN_PATH.
What it said when it did not start
Resolved configuration: transport: stdio (default) enabledTools: all (default) debug: false (default) credentials: package default (gcp-oauth.keys.json) (default) tokenPath: /tmp/.config/google-calendar-mcp/tokens.json (default) accountMode: normal (default) Authenticating with OAuth client credentials from /app/node_modules/@cocal/google-calendar-mcp/gcp-oauth.keys.json Failed to start server: Error loading OAuth keys: OAuth credentials not found. Please provide credentials using one of these methods: 1. Environment variable: Set GOOGLE_OAUTH_CREDENTIALS to the path of your credentials file: export GOOGLE_OAUTH_CREDENTIALS="/path/to/gcp-oauth.keys.json" 2. Default file path: Place your gcp-oauth.keys.json file in the package root directory. Token storage: - Tokens are saved to: /tmp/.config/google-calendar-mcp/tokens.json - To use a custom token location, set GOOGLE_CALENDAR_MCP_TOKEN_PATH environment variable To get OAuth credentials: 1. Go to the Google Cloud Console (https://console.cloud.google.com/) 2. Create or select a project 3. Enable the Google Calendar API 4. Create OAuth 2.0 credentials 5. Download the credentials file as gcp-oauth.keys.json Credentials file: /app/node_modules/@cocal/google-calendar-mcp/gcp-oauth.keys.json Original error: ENOENT: no such file or directory, open '/app/node_modules/@cocal/google-calendar-mcp/gcp-oauth.keys.json'
Written by the package or by npm, not by this site.
Install facts
| License | MIT |
|---|---|
| Needs | node >=20 |
| Source | github.com/nspady/google-calendar-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-NQdZ/OdJJ8CQJtpg/GhMI2k8Mq0TaaAcagE9WOzI9xtR9SBB5DGeNc8D4kwNB5KqXMdjI5q+U6dx+bkFwaWzJg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40cocal/google-calendar-mcp)
New version out? Ask for a fresh report.