Complete reference for MCP JSON-RPC error codes (-32000 to -32099 and 32600-32603), including meanings, common causes, and troubleshooting steps for each error code.
MCP (Model Context Protocol) uses JSON-RPC 2.0 with standard error codes. This article provides complete error code reference and troubleshooting guide.
| Code | Name | Description |
|---|---|---|
| -32700 | Parse error | JSON parsing failed |
| -32600 | Invalid Request | Invalid request format |
| -32601 | Method not found | Method doesn't exist |
| -32602 | Invalid params | Invalid parameters |
| -32603 | Internal error | Internal error |
| Code | Name | Description |
|---|---|---|
| -32000 | Server error | MCP Server internal error |
| -32001 | Connection error | Connection error |
| -32002 | Timeout error | Operation timeout |
| -32003 | Resource not found | Resource doesn't exist |
| -32004 | Resource expired | Resource expired |
| -32005 | Invalid resource | Invalid resource |
{
"jsonrpc": "2.0",
"error": {
"code": -32600,
"message": "Invalid Request: missing method field"
},
"id": 1
}
Auto-repair applied and deterministic inspection checks passed.
排查流程完整
错误码参考准确