tool · inferred from evidence
npx
Node.js package runner
- AADSTS700082: the teams-mcp refresh token expired after long idle
Fixes teams-mcp failing after weeks of disuse with an AADSTS refresh-token error. Use when auth worked, then broke after a long gap. Not for fresh-install login failures.
- Authentication failed: device_code_expired: Device code is expired. (teams-mcp)
Fixes the teams-mcp authenticate command failing with an expired device code. Use when npx @floriscornel/teams-mcp authenticate fails right after login. Not for AADSTS errors or missing licenses.
- Tenant config as code: auth0-deploy-cli and the Terraform provider
Click-ops tenants drift. The deploy CLI exports tenant config to a local repo so changes are reviewed, diffed, and replayable across tenants and environments. Not the full reference manual.
- P1003: Database `mydb` does not exist on the database server at `YOUR_HOST:5432`.
Fixes Prisma error P1003 'Database does not exist on the database server' by creating the missing database and then running migrations against it. Use when the server is reachable and credentials work but the named database was never create
- P3018: A migration failed to apply. New migrations cannot be applied before the error is recovered from.
Fixes Prisma error P3018 'A migration failed to apply' by deciding whether the failed migration's changes actually landed, then marking it rolled back or applied with migrate resolve. Use when migrate deploy stops with P3018 and new migrati
- P3006: Migration `20240101_init` failed to apply cleanly to the shadow database.
Fixes Prisma error P3006 'Migration failed to apply cleanly to the shadow database' by finding the SQL in the migration that the empty shadow database cannot run, usually generated columns, extensions, or permissions, and rewriting it. Use
- P1001: Can't reach database server at `YOUR_HOST`:`5432`
Fixes Prisma error P1001 'Can't reach database server' by diagnosing which part of the connection path is wrong: host, port, pooler mode, or a server that is not actually running. Use when Prisma fails to open any connection at all. Not for
- Postgres MCP: MCP error -32603 self-signed certificate in certificate chain (RDS)
Fixes the Postgres MCP server failing against AWS RDS with a self-signed certificate error. Use when tool calls fail with MCP error -32603: self-signed certificate in certificate chain against RDS or another SSL-mandatory host. Not for wron
- Perplexity MCP: PERPLEXITY_API_KEY is required
Fixes the Perplexity MCP server refusing to start with a missing-key error. Use when the server exits immediately with PERPLEXITY_API_KEY is required, which means the key never reached the server process. Not for 401 errors from Perplexity'
- Brave Search MCP: 422 SUBSCRIPTION_TOKEN_INVALID
Fixes the Brave Search MCP server failing every query with a 422 subscription token error. Use when searches return 422 SUBSCRIPTION_TOKEN_INVALID, which means the BRAVE_API_KEY is missing, wrong, or not reaching the server. Not for wrong p
- firecrawl-mcp: Unexpected token 'D', "[DEBUG] 202"... is not valid JSON
Fixes the firecrawl MCP server failing in Claude Desktop with a JSON parse error caused by debug log lines on stdout. Use when the server shows connected but immediately errors with Unexpected token 'D' and a [DEBUG] prefix. Not for missing
- npm error could not determine executable to run (exa-mcp-server)
Fixes the exa-mcp-server install failure where npx reports it cannot determine an executable to run. Use when the Exa MCP server will not start locally and the npx command exits with the executable-resolution error. Not for missing API key