Send MCP JSON-RPC message

curl --request POST \ --url https://api.stackone.com/mcp \ --header 'Accept: <accept>' \ --header 'Authorization: Basic <encoded-value>' \ --header 'Content-Type: application/json' \ --data ' { "jsonrpc": "2.0", "method": "initialize", "params": { "clientInfo": { "name": "my-client", "version": "1.0.0" }, "protocolVersion": "2025-11-25", "capabilities": {} }, "id": "init-1" } '

{ "jsonrpc": "2.0", "id": "init-1", "result": { "protocolVersion": "2025-11-25", "capabilities": { "tools": { "listChanged": true } }, "serverInfo": { "name": "stackone-mcp-server", "version": "1.0.1", "title": "StackOne", "description": "Give AI agents 30,000+ safe, token-optimized actions across Workday, SAP, Oracle + hundreds more.", "websiteUrl": "https://www.stackone.com", "icons": [ { "src": "https://stackone-logos.com/api/stackone/icon/png", "mimeType": "image/png", "sizes": [ "200x200" ] }, { "src": "https://www.stackone.com/favicon.svg", "mimeType": "image/svg+xml", "sizes": [ "any" ] } ] } } }

Authorizations

Authorization

string

header

required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Headers

x-account-id

string

Account secure id for the target provider account. With an API key, a comma-separated list of up to 50 of them lists and runs tools across several accounts (optional if x-account-id query parameter is provided)

string

default:application/json, text/event-stream

required

Must list both application/json and text/event-stream, which the Streamable HTTP spec requires of a client; anything else is rejected with 406. The response itself is always application/json: this server answers in JSON mode and never opens an SSE stream.

Example:

"application/json, text/event-stream"

Query Parameters

apps

enum<string>

MCP Apps panel: "off" (default) omits it, "on" registers the interactive toolset explorer. Only set it for hosts that render MCP Apps — a client with no iframe (a terminal) gets a tool whose result it cannot display

Available options:

on,

off

instructions

enum<string>

Server instructions (returned in the MCP initialize handshake) that teach the model the path/query/body/headers parameter envelope: "off" (default) omits them, "on" includes envelope guidance matched to the active param-style

Available options:

on,

off

param-style

enum<string>

Parameter schema style: "flat_prefixed" (default) flattens with location prefix, "nested" groups by location, "flat_smart" flattens and only prefixes on name collision

Available options:

nested,

flat_prefixed,

flat_smart

tool-mode

enum<string>

Tool registration mode: "individual" (default) registers each action as a separate tool; "search_execute" registers two tools per linked account for a search-then-execute flow

Available options:

individual,

search_execute

Body

application/json

JSON-RPC 2.0 message

jsonrpc

string

required

JSON-RPC protocol version

Example:

"2.0"

method

string

required

JSON-RPC method name. Supported values: initialize, tools/list, tools/call.

Example:

"initialize"

params

object | null

Method parameters. Shape varies by method — see the request body examples.

Request id (string or number). Echoed back in the response.

Response

Processed successfully

jsonrpc

string

Example:

"2.0"

Echoes the id from the request. null for protocol-level errors where the id could not be determined.

result

any | null

Present on success. Shape varies by method — see response examples.

error

object

Present on protocol-level failure. Tool-level failures use result with isError: true instead.

Show child attributes

Accounts

Actions

Connect Sessions

Connector Profiles

Connectors

Data Sync

Logs

MCP

Webhooks

Send MCP JSON-RPC message

Authorizations

Headers

Query Parameters

Body

Response