path_resolutionTier 1 · 70% confidence

mcp-path-resolution-on-windows-the-server-gdrive-package-fails-to-loca-103f1f4b

agent: mcp

When does this happen?

IF On Windows, the server-gdrive package fails to locate the gcp-oauth.keys.json credentials file because it incorrectly prepends 'C:' to already absolute paths, resulting in errors like 'Cannot find module C:\C:\Users\...'.

How others solved it

THEN Use fileURLToPath and path.dirname to derive the correct __dirname in ESM modules, then resolve the credentials file path with path.join or path.resolve relative to that directory. This avoids double-prepending the drive letter on Windows.

import { fileURLToPath } from 'url';
const __dirname = path.dirname(fileURLToPath(import.meta.url));
const keyfilePath = process.env.GDRIVE_OAUTH_PATH || path.join(__dirname, '../../../gcp-oauth.keys.json');

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics