MCP JSON-RPC endpoint
Model Context Protocol endpoint. Speaks JSON-RPC 2.0 with methods:
initialize, tools/list, tools/call, ping.
Correlation: every tools/call result carries the request id under
the spec-level _meta.requestId (same value as the X-Request-ID
response header); JSON-RPC error responses carry it under error.data.requestId.
Idempotency: a mutating tools/call may supply an Idempotency-Key
— either the HTTP header below, or params._meta.idempotencyKey. A repeat
call with the same key and identical arguments replays the original
result; the same key with different arguments returns a JSON-RPC error
(code -32009). Read-only tools ignore the key. Keys live for 24 hours.
Authorizations
API key or personal access token (NEX-1042). Send as
Authorization: Bearer <token>. Token format:
nex_live_…— live API key (server-to-server)nex_test_…— sandbox API keynex_pat_…— personal access token (acts as the issuing user)
Authorization is decided by the key's scopes array, not the
owning user's RBAC role. See POST /api/api-keys to mint a key.
Headers
Optional idempotency key for a mutating tools/call. Also accepted as params._meta.idempotencyKey in the JSON-RPC body.
255
