jsonrpc.ts

Following MCP, Zzz supports a subset of JSON-RPC 2.0 as its message format (A2A too, but I haven't looked into if they support the full spec). It can be used by multiple transports including http and websocket.

These are the JSON-RPC types from the MCP draft in May 2025, changed to include a prefix on all identifiers. It's also defined with Zod schemas instead of plain TS like the MCP library.

MCP messages are a subset of JSON-RPC:

- params does not support the positional array format, and result supports only object values, instead of being any JSON value. - MCP does not support batching, see https://github.com/modelcontextprotocol/modelcontextprotocol/pull/416 and https://github.com/modelcontextprotocol/modelcontextprotocol/pull/228

@source https://github.com/modelcontextprotocol/typescript-sdk @see https://modelcontextprotocol.io/ @license https://github.com/modelcontextprotocol/typescript-sdk/blob/main/LICENSE

MIT License

Copyright (c) 2024 Anthropic, PBC

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

30 declarations

view source