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

# MCP server

> Connect AI assistants like Claude, Cursor, and Windsurf to your Ravenna workspace through the Model Context Protocol to manage tickets and users.

<Panel>
  <Callout icon="flask-conical" color="#7C3AED">
    This feature is currently in Beta. We appreciate all feedback to help us improve this feature, so please share via Slack or via [support@ravenna.ai](mailto:support@ravenna.ai).
  </Callout>
</Panel>

The Ravenna MCP server lets AI assistants interact directly with your workspace through the <Tooltip tip="Model Context Protocol: an open standard that lets AI assistants connect to external tools and data sources through a unified interface." headline="MCP" cta="Learn about MCP" href="https://modelcontextprotocol.io">Model Context Protocol</Tooltip>. Instead of switching between your AI tool and the Ravenna web app, you can manage tickets, look up users, configure access policies, and more from a single conversation.

The server works with ChatGPT, Claude Code, Codex, Cursor, VS Code, and any other MCP client that supports OAuth. Sign in with your Ravenna account using OAuth to securely authenticate and access your workspaces.

***

## What you can do

<CardGroup cols={2}>
  <Card title="Manage tickets" icon="ticket">
    Create, update, search, and triage tickets. Add messages, change statuses, apply tags, and link related tickets.
  </Card>

  <Card title="Automate workflows" icon="zap">
    Create and manage code actions, task templates, and automated processes across your workspace.
  </Card>

  <Card title="Manage users and access" icon="users">
    Look up users, manage group memberships, configure access policies, and handle access requests.
  </Card>

  <Card title="Configure workspace" icon="settings">
    Set up channels, categories, custom fields, ticket statuses, and other workspace settings.
  </Card>
</CardGroup>

***

## How it works

The MCP server exposes Ravenna's API as a set of tools that AI assistants can discover and call. Your AI client connects to a single <Tooltip tip="A specific URL where your AI client sends requests to communicate with Ravenna's MCP server." headline="Endpoint">endpoint</Tooltip> (`/mcp`) over HTTPS using <Tooltip tip="A transport method where your AI client sends standard HTTP requests to a single URL. No persistent connection needed." headline="Streamable HTTP">Streamable HTTP</Tooltip>. You do not need to choose or configure a transport yourself.

OAuth-capable clients like ChatGPT and Claude discover Ravenna's authorization server from the MCP endpoint and sign you in with your existing Ravenna account. Your AI assistant accesses only the data and workspaces that your user account is authorized to see.

***

## Permissions and workspace targeting

The MCP server enforces your existing Ravenna roles on every tool call. Your assistant can only do what your account is allowed to do in the Ravenna web app.

* **Workspace tools** (most tools, including tickets, channels, custom fields, and task templates) require you to be a member of the target workspace with an allowed role. Most workspace tools allow both Admin and Member roles; some configuration tools are limited to Admins.
* **Organization tools** (such as creating users) require organization admin privileges.
* **Guests** (organization members without workspace membership) cannot call workspace tools for that workspace.

If your role does not permit a tool, the call returns a forbidden error and your assistant reports that you do not have access.

### Targeting a workspace

Because your account can span multiple workspaces, your assistant must know which workspace each call applies to. For workspace tools, the AI client passes a `workspaceId` parameter on every call.

* **OAuth connections** can reach any workspace you are a member of. Tell your assistant which workspace to use, for example: *"In the IT Support workspace, list open tickets assigned to me."* Your assistant resolves the workspace and supplies the ID automatically.
* **API key connections** are pinned to the workspace that issued the key. Calls targeting any other workspace are rejected, even if you are a member of it. Use OAuth if you need to work across multiple workspaces in a single session.

***

## Use cases

Because MCP is an open standard, you can pair the Ravenna server with other MCP servers your AI client is connected to. This means your assistant can pull context from multiple systems in a single conversation.

**Create tickets enriched with context from other tools**

> "Look up Jamie Lee in HiBob, then create an onboarding ticket in the IT Support channel with their department, start date, and manager."

Your AI assistant can pull data from other MCP-connected services like <Tooltip tip="An HR platform for managing employee data, onboarding, and people operations." headline="HiBob" cta="View HiBob integration" href="/integrations/hibob/overview">HiBob</Tooltip>, Slack, or your calendar and use that context to create detailed tickets in any Ravenna workspace without you copying and pasting between apps.

**Review channels and find tickets that need attention**

> "Show me open tickets in the IT Support channel that have been waiting more than 48 hours. Which ones are unassigned?"

Quickly scan your channels for stale or unassigned tickets. Your assistant summarizes what is waiting, highlights anything overdue, and helps you decide what to pick up or reassign.

**Plan your day with your AI assistant**

> "What tickets are assigned to me across all my workspaces? Prioritize them by due date and flag anything that is overdue."

Use your AI assistant as a personal task tracker. Ask it to pull your assigned tickets, summarize where things stand, and help you decide what to work on next. As you work through your list, update statuses and add messages without leaving the conversation.

**Bulk update tickets and close out incidents**

> "Pull the resolution notes from the DNS outage post-mortem in Incident.io, then post a summary message on all open tickets tagged 'dns-outage' and move them to Resolved."

Handle incident follow-up in a single conversation. Your assistant can pull context from another MCP-connected service like <Tooltip tip="An incident management platform for declaring, coordinating, and resolving incidents." headline="Incident.io" cta="View Incident.io integration" href="/integrations/incident-io/overview">Incident.io</Tooltip>, draft a stakeholder update, apply it across affected tickets, and bulk-update statuses, categories, or tags to keep your workspace organized.

<Callout icon="link" color="#6B7280">
  Ready to connect? Follow the [setup guide](/documentation/automate/mcp/setup) to configure your AI client.
</Callout>