Skip to main content
AI agents and automated tools integrate with orriven through two distinct interfaces, separated by authorization model and operational scope:
Integrated workflow: Connect the MCP server, invoke create_api_key to generate a secret key for the target Business Unit, and configure the agent to execute event data operations against the Developer API.

MCP server

The MCP server implements the Model Context Protocol over Streamable HTTP with OAuth 2.1 authentication, supporting clients such as Claude.ai connectors, Claude Code, Cursor, and custom MCP SDK implementations. Upon client connection and user consent, the client receives a short-lived access token with automatic renewal during active sessions. Tool execution strictly reflects the authorizing user’s organization and Business Unit role permissions.
  • Connect an agent — Configuration guide for Claude.ai, Claude Code, and standard MCP clients.
  • Tools — Tool definitions, input parameters, and response schemas.
  • Recipes — Common automation workflows for key provisioning, webhook diagnostics, and incident response.
  • Security & authorization — Authorization scopes, token lifecycles, and audit logging.
Building an event site with an agent? Install the orriven skills/plugin marketplace add orriven/skills in Claude Code, or npx skills add orriven/skills — and the agent knows how to connect, bind a project to a Business Unit, scaffold a complete Next.js site against the APIs and hosted pages, and verify it end to end.

Developer API

Automated workflows interacting with event data—such as querying ticket capacity, approving attendee registrations, or creating orders—use the Developer API directly via Authorization: Bearer osk_… against https://openapi.orriven.com/v1. For complete resource schemas and endpoint specifications, refer to the Developer API overview and the OpenAPI specification at /openapi.json.
The MCP server provides management and developer platform tools. Event data operations are served through the unified REST Developer API to maintain consistency across integrations.