Protocol details - Groovin


Address	`https://api.groovin.ai/functions/v1/mcp-server`
Transport	Streamable HTTP: JSON-RPC 2.0 over `POST`, one JSON answer per request
Protocol version	`2025-06-18`. `initialize` answers with the version your client sends
Sessions	None: each request stands alone
Streaming	None: no server-sent events
Sign-in	`Authorization: Bearer` with an API key or an OAuth token

Supported methods

Method	What it does
`initialize`	Starts the connection and returns the server’s instructions
`ping`	Checks the server is there
`tools/list`	Lists every tool, in one page
`tools/call`	Runs a tool

The server only offers tools: no prompts and no resources. Notifications get an empty 202 answer, and JSON-RPC batches are accepted.

Tools

Each tool declares a JSON Schema for its arguments and its answer, and hints such as readOnlyHint. These hints help your client decide what needs a human confirmation: they do not replace reading what each call does. The answer schema only covers top-level fields. See Data models for the full objects.

Answers

A successful tools/call returns the answer twice, as JSON text in content[0].text and as an object in structuredContent. A failed tool call still answers HTTP 200, with isError: true and the message in content. See MCP errors.

JSON-RPC errors

Code	Meaning
`-32700`	The body is not valid JSON
`-32600`	The request is not valid JSON-RPC
`-32601`	Unknown method
`-32602`	Invalid parameters, such as a missing tool name

Any method other than POST gets a 405.