MCP Error Decoder
Search exact error strings and stack traces from Claude Desktop, Cursor, and OpenAI Codex CLI. Inspect root causes and copy verified terminal fixes.
JSON-RPC error -32602: Invalid params
Server rejects tool invocation stating arguments do not match schema.
The AI model passed arguments with incorrect data types (e.g. string instead of integer or array), or omitted a required parameter defined in inputSchema.
Inspect the tool's inputSchema with tools/list and ensure all required fields match their declared types.
# Inspect tool schema via MCP inspector:
npx @modelcontextprotocol/inspector# Inspect tool schema via MCP inspector:
npx @modelcontextprotocol/inspector# Inspect tool schema via MCP inspector:
npx @modelcontextprotocol/inspector// Ensure payload arguments match required properties
{
"jsonrpc": "2.0",
"id": 12,
"method": "tools/call",
"params": {
"name": "query_database",
"arguments": {
"limit": 10 // Number, not string "10"
}
}
}Architecture of Model Context Protocol Failures
MCP server issues typically stem from process isolation mismatches, stdio stream contamination, or environment inheritance limitations. Because the host AI application communicates across child-process stdio pipes or Server-Sent Events (SSE) connections, traditional browser debugging tools cannot directly capture errors.
Stdio vs. Stderr Separation
The primary rule of local MCP servers is that STDOUT belongs exclusively to the JSON-RPC wire protocol. If a server library outputs diagnostic logs, banner messages, or package notices to STDOUT, the host JSON parser crashes with an unrecoverable framing error. All server logging must route to STDERR.
GUI Subprocess Environment Isolation
Desktop GUI hosts (such as Claude Desktop or Cursor) are launched by the desktop window manager, not your shell profile (.bashrc or .zshrc). They inherit a minimal system PATH. Tools installed via nvm, pyenv, or Homebrew often require absolute binary paths in the configuration.