Whatever message this page gives is out now! Go check it out!
JSON-RPC protocol errors
Last update:
May 18, 2026
JSON-RPC protocol errors occur when an MCP request message is invalid or cannot be processed at the protocol level, independent of any specific tool or business logic.
Overview
The MCP protocol uses JSON-RPC 2.0 for all method calls, such as
initialize, tools/list, tools/call, and resources/read. JSON-RPC errors indicate that the protocol message itself was malformed, incomplete, or otherwise invalid, and therefore could not be processed by the MCP server. Common causes
- Malformed JSON in the request body
- Missing required JSON-RPC fields (
jsonrpc,method, orid) - Unknown or unsupported method names
- Invalid parameter structure or incorrect data types at the protocol level
How JSON-RPC errors surface
When a protocol-level error occurs, the MCP server returns a JSON-RPC error object. Common error codes include:
-32600(Invalid Request)-32601(Method not found)-32602(Invalid params)-32603(Internal error)
Recommended response
- Treat JSON-RPC errors as client or integration defects rather than business-level errors.
- Review the ColdFusion MCP client implementation for:
- Incorrect method names (for example,
tools/listortools/call) - Incorrect parameter structures or missing required fields
- Non-JSON-serializable values in arguments
- Incorrect method names (for example,
- Log the complete JSON-RPC error response for debugging purposes.
- Do not retry automatically with the same invalid payload.
We're glad. Tell us how this page helped.
We're sorry. Can you tell us what didn't work for you?
Share additional feedback to help us improve.
0/255
|
