MCP session teardown (no longer applicable)

DELETE

/mcp-bot

const url = 'https://example.com/api/mcp-bot';
const options = {method: 'DELETE', headers: {cookie: 'sb-access-token=<sb-access-token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url https://example.com/api/mcp-bot \
  --cookie sb-access-token=<sb-access-token>

A 2025-era session teardown. Stateless serving holds no session, so there is nothing to tear down and the request is answered 405. An unauthenticated caller still receives the 401 challenge.

Authorizations

cookieAuth

Responses

401

Not authenticated

application/json

object

error

required

Human-readable error message

string

code

Stable machine-readable error code for client branching

string

fieldErrors

First validation message per field path

object

key

additional properties

string

issues

Structured validation issues (Zod)

Array<object>

object

path

required

string

message

required

string

retryAfter

Seconds until rate limit resets (429 responses)

number

reconnect

True if re-linking GitHub may fix the issue

boolean

405

No session to delete.