Model Context Protocol (MCP) endpoint
Changed onJSON-RPC 2.0 endpoint implementing the Model Context Protocol. The server is stateless — each request is independent, no session management.
Supported methods: initialize, tools/list, tools/call. The tool catalogue is curated (read and write). tools/list returns only the tools this credential can call. Names use {resource}.{action} (for example contacts.search).
Authentication
Three accepted sources (first one set wins):
- URL path parameter — POST /mcp/{token} (see the dedicated operation below)
- Query string — POST /mcp?token=…
- Authorization header — POST /mcp (recommended)
See the mcp tag description for transport headers (Accept), JSON responses, HTTP 400 transport errors, the tool catalogue, parameters, and permission requirements.
Request
- Base URLhttps://public-api.ringover.com/v2
- URLhttps://public-api.ringover.com/v2/mcp
- Auth
- API key in header Authorization
- or API key in query parameter token
Headers
Must include both application/json and text/event-stream (comma-separated). Example: application/json, text/event-stream.
Request body
Response
JSON-RPC response (Content-Type: application/json). On success, the result field contains the method output.
For supported methods, protocol and tool errors use HTTP 200: JSON-RPC error (for example tool rate limit) or a tools/call result with isError: true (forbidden, not found, invalid input). Unknown method names and other transport-level failures are not included here — they return HTTP 400 (see below).
Changes
- breaking
added the new required
headerrequest parameterAccept - info
added the non-success response with the status
- breaking
- info
endpoint added
- info