DEVELOPER PORTAL

Build with gibeon.io

One OAuth token, two surfaces: a typed REST API and a hosted MCP for AI agents. Wire your stack into the screens you already have. No extra hardware, no proprietary SDK.

Quickstart (5 min) →

REST API

Bearer-authenticated endpoints on www.gibeon.io/v1 covering players, playlists, sequences, planning, and assets. 60 req/min per token.

View reference →

Or grab the raw OpenAPI 3.1 spec for Postman, Bruno, or codegen.

Hosted MCP

13 tools at www.gibeon.io/mcp for Claude Desktop, Claude Code, Cursor. Zero install. The client authorizes itself via OAuth.

{
  "mcpServers": {
    "gibeon": {
      "url": "https://www.gibeon.io/mcp"
    }
  }
}

npm package

@gibeon/mcp-server is deprecated: the stdio variant used the removed gib_live_ keys.

View on npm →

npx -y @gibeon/mcp-server is deprecated. Use the hosted MCP.

Get an access token

Auth is OAuth 2.1 (Authorization Code + PKCE), issued by Supabase. Authorize gibeon.io from your client, approve the consent screen, and pick your tenant. The full flow lives at www.gibeon.io/auth.md.

What's here today

Quickstart: key to first publish in 5 minutes.
REST reference: every endpoint with examples + try-it.
MCP tools: all 13 tools with descriptions and JSON input schemas.
npm package as a compat shim for stdio-only MCP hosts.

What's coming

Dedicated guides for rate-limits and errors, and a recipe book for common integrations (n8n, Zapier, raw fetch). Until those land, the API and MCP helpcenter article covers most common questions.