Skip to main content
GET
/
sse
/
{mcp_server_name}
SSE server proxy endpoint
curl --request GET \
  --url https://{organization_id}.mcp.barndoor.ai/sse/{mcp_server_name} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "event_types": [
    "data_update",
    "status_change"
  ],
  "filters": {
    "object_type": "Account",
    "limit": 100
  }
}
'
"event: connected\ndata: {\"status\": \"ready\", \"timestamp\": \"2024-01-01T00:00:00Z\"}\n\nevent: data_update\ndata: {\"type\": \"Account\", \"id\": \"123\", \"name\": \"Acme Corp\"}\n\nevent: status_change\ndata: {\"status\": \"disconnected\", \"reason\": \"timeout\"}\n"

Authorizations

​
Authorization
string
header
required

JWT token obtained through Auth0 OAuth 2.0 flow with PKCE.

The token should be included in the Authorization header: Authorization: Bearer <your-jwt-token>

Use the Barndoor SDK's loginInteractive() function to obtain tokens automatically.

Headers

​
x-mcp-session-id
string

MCP session identifier for request tracking

Path Parameters

​
mcp_server_name
string
required

MCP server name identifier

Body

application/json

Optional request payload for SSE initialization

SSE initialization parameters

​
event_types
string[]

Types of events to subscribe to

Example:
["data_update", "status_change"]
​
filters
object

Event filtering parameters

Example:
{ "object_type": "Account", "limit": 100 }

Response

SSE event stream

Server-Sent Events stream for real-time communication.

Events follow the SSE format with optional event types and data payloads.

Example events:

event: connected
data: {"status": "ready", "timestamp": "2024-01-01T00:00:00Z"}

event: data_update
data: {"type": "Account", "id": "123", "changes": {...}}

event: error
data: {"error": "rate_limit", "message": "Rate limit exceeded"}