Build with Gibeon | Gibeon

Build with Gibeon

One API key, 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 api.gibeon.io/v1 covering players, playlists, sequences, planning, and assets. 60 req/min per key.

View reference →

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

Hosted MCP

13 tools at api.gibeon.io/mcp for Claude Desktop, Claude Code, Cursor. Zero install. Same Bearer key as REST.

{
  "mcpServers": {
    "gibeon": {
      "url": "https://api.gibeon.io/mcp",
      "headers": {
        "Authorization": "Bearer gib_live_…"
      }
    }
  }
}

npm package

@gibeon/mcp-server ships the same 13 tools as a local stdio process. Use it when your MCP host does not yet support remote transports.

View on npm →

npx -y @gibeon/mcp-server and pass GIBEON_API_KEY in env.

Get a key

Open the CMS at app.gibeon.io and go to Settings → API → New key. The full gib_live_… value is shown once at creation.

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.