Skip to content

Developers

This track covers the REST API, the AI/MCP integration, and OAuth. The REST API is the single contract; the AI/MCP integration and the apps are all clients of it.

What you can build against

  • REST API: events, directory, rooms, and relationships. Every permission and plan gate applies the same way it does in the apps. (Reference porting from docs/API_REFERENCE_*.md.)
  • AI / MCP: a client-agnostic remote MCP server that lets any AI client (Claude, ChatGPT, Cursor, custom agents) act on a workspace’s behalf, using task-first tools and a preview→confirm contract. (Porting from docs/integrations/MCP.md.)
  • OAuth 2.1: an in-house authorization server with dynamic client registration, PKCE, and scoped, workspace-bound tokens.

Vocabulary

This track uses the team-canonical terms (e.g. Entity, ManagedEntity) because they match the API surface. The Glossary maps those to the words users see.

For users

The user-facing guide to connecting an assistant, what it can do and what it deliberately leaves to a person, is AI assistants.

Gating

Every plan can connect an AI assistant and make changes through it. The plan’s own limits (confirmed shows, shows with other Showliner accounts on the bill) apply to what an assistant does, exactly as they do in Showliner. See plan comparison.