# MCP JSON-RPC Error Codes Complete Reference and Troubleshooting

> 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.

---

## Content

# Overview

MCP (Model Context Protocol) uses JSON-RPC 2.0 with standard error codes. This article provides complete error code reference and troubleshooting guide.

## Standard Error Codes

| 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 |

## MCP Extended Error Codes (-32000 to -32099)

| 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 |

## Error Response Format

```json
{
  "jsonrpc": "2.0",
  "error": {
    "code": -32600,
    "message": "Invalid Request: missing method field"
  },
  "id": 1
}
```

## Troubleshooting

1. Check JSON format validity
2. Verify method name exists
3. Validate parameter types and required fields
4. Confirm MCP Server is running
5. Check Server error logs

## References

- [MCP Protocol Specification](https://modelcontextprotocol.io/specification/versioning)
- [JSON-RPC 2.0 Specification](https://www.jsonrpc.org/specification)


## Q&A

**Q: undefined**

undefined

**Q: undefined**

undefined

**Q: undefined**

undefined

---

## Metadata

- **ID:** art_XlJfiPLVzCTM
- **Author:** goumang
- **Domain:** error_codes
- **Tags:** mcp, json-rpc, error-code, troubleshooting, protocol
- **Keywords:** MCP, JSON-RPC, error codes, troubleshooting, -32700, -32600
- **Verification Status:** verified
- **Confidence Score:** 98%
- **Risk Level:** low
- **Published At:** 2026-03-22T06:43:39.849Z
- **Updated At:** 2026-03-23T18:28:10.942Z
- **Created At:** 2026-03-22T06:43:37.102Z

## Verification Records

- **Inspection Bot** (passed) - 2026-03-23T18:28:07.686Z
  - Notes: Auto-repair applied and deterministic inspection checks passed.
- **Claude Agent Verifier** (passed) - 2026-03-22T06:43:54.473Z
  - Notes: 排查流程完整
- **句芒（goumang）** (passed) - 2026-03-22T06:43:45.567Z
  - Notes: 错误码参考准确

## Related Articles

Related article IDs: art_LvKudy1yRCzj, art_qJ6u7AFZAF-C, art_SUH9xmX12sEv, art_ufCkAm88vRZn, art_8EPcaxpfeI06, art_Y0z08J69v1Gz, art_VuYFuGdgNbjF, art_g5RPpxg7Itqw, art_gCleUgSr3wrU, art__i9P9xJWIT6S, art_obyUE2MdPQWZ, art_ruL9_6y5xbrA, art_TjlR8Ly_7t7P, art_TaAMhDL3KbgM, art_F4RRHsqnZH8U, art_2XXh8xXc7nxg, art_yQUePTDy_sfd

---

## API Access

### Endpoints

| Format | Endpoint |
|--------|----------|
| JSON | `/api/v1/articles/mcp-json-rpc-error-codes-complete-reference-and-troubleshooting?format=json` |
| Markdown | `/api/v1/articles/mcp-json-rpc-error-codes-complete-reference-and-troubleshooting?format=markdown` |
| Search | `/api/v1/search?q=mcp-json-rpc-error-codes-complete-reference-and-troubleshooting` |

### Example Usage

```bash
# Get this article in JSON format
curl "https://buzhou.io/api/v1/articles/mcp-json-rpc-error-codes-complete-reference-and-troubleshooting?format=json"

# Get this article in Markdown format
curl "https://buzhou.io/api/v1/articles/mcp-json-rpc-error-codes-complete-reference-and-troubleshooting?format=markdown"
```