> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agents on orriven

> Integration architecture for AI agents: Model Context Protocol (MCP) server for management workflows and Developer API for event operations.

AI agents and automated tools integrate with orriven through two distinct interfaces, separated by authorization model and operational scope:

| Dimension                    | MCP server                                                                                        | Developer API                                                                                        |
| ---------------------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Identity & authorization** | Delegated user authorization via OAuth 2.1                                                        | Service credential via API key (`osk_…`)                                                             |
| **Operational scope**        | Developer resources: API keys, webhooks, request logs, metrics, organizations, and Business Units | Event data: events, ticket types, registrations, redemption codes, orders, check-ins, and exhibitors |
| **Authentication flow**      | Browser consent via OAuth 2.1 (once per client)                                                   | HTTP Bearer token                                                                                    |
| **Installation**             | Standard HTTPS endpoint (`https://api.orriven.com/mcp`)                                           | Standard REST HTTPS endpoint (`https://openapi.orriven.com/v1`)                                      |
| **Audit trail**              | Authorizing user account, marked *via MCP*                                                        | Scoped API key identifier                                                                            |

<Info>
  **Integrated workflow**: Connect the [MCP server](/en/agent/connect), 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](/en/developers/overview).
</Info>

## MCP server

```text theme={null}
https://api.orriven.com/mcp
```

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](/en/agent/connect) — Configuration guide for Claude.ai, Claude Code, and standard MCP clients.
* [Tools](/en/agent/tools) — Tool definitions, input parameters, and response schemas.
* [Recipes](/en/agent/recipes) — Common automation workflows for key provisioning, webhook diagnostics, and incident response.
* [Security & authorization](/en/agent/security) — Authorization scopes, token lifecycles, and audit logging.

<Tip>
  **Building an event site with an agent?** Install the [orriven skills](https://github.com/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.
</Tip>

## 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](/en/developers/overview) and the OpenAPI specification at `/openapi.json`.

<Note>
  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.
</Note>