Ravenna MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ravenna MCP Server create a high priority ticket for a login bug"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ravenna MCP Server
This is a Model Context Protocol (MCP) server for the Ravenna help desk platform, allowing LLMs to create, update, and retrieve tickets directly from Ravenna.
Features
Create tickets with title, description, priority, and tags
Update existing tickets (title, description, status, priority, etc.)
List tickets with various filters (status, priority, assignee, tags)
Get detailed information about specific tickets
Related MCP server: MCP Movidesk Server
Setup
Clone the repository
Install dependencies:
npm install
# or
bun installSet your Ravenna API key as an environment variable:
export RAVENNA_API_KEY=your_api_key_hereRunning the Server
bun run index.ts
# or
npm run startThe server runs on stdio, making it compatible with MCP clients like Claude Desktop or other MCP-enabled applications.
Tools
Create Ticket
Creates a new ticket in Ravenna.
Required fields:
title: The title of the ticketdescription: A detailed description of the ticket
Optional fields:
priority: Ticket priority (low, medium, high, urgent)tags: Array of string tags to categorize the ticket
Example:
{
"title": "Website login issue",
"description": "Users are unable to log in to the customer portal after the latest update.",
"priority": "high",
"tags": ["website", "login", "customer-portal"]
}Update Ticket
Updates an existing ticket in Ravenna.
Required fields:
id: The ID of the ticket to update
Optional fields:
title: Updated title of the ticketdescription: Updated description of the ticketstatus: Updated status (open, in_progress, pending, resolved, closed)priority: Updated priority (low, medium, high, urgent)assignee: User ID to assign the ticket totags: Updated tags for the ticket
Example:
{
"id": "12345",
"status": "in_progress",
"assignee": "user_id_123",
"priority": "high"
}List Tickets
Lists tickets in Ravenna with optional filters.
Optional fields:
status: Filter by ticket status (open, in_progress, pending, resolved, closed, all)priority: Filter by ticket priority (low, medium, high, urgent, all)assignee: Filter by assignee user IDtags: Filter by tags (any match)limit: Maximum number of tickets to return
Example:
{
"status": "open",
"priority": "high",
"limit": 10
}Get Ticket
Get detailed information about a specific ticket.
Required fields:
id: The ID of the ticket to retrieve
Example:
{
"id": "12345"
}API Reference
This server uses the Ravenna API, as documented in https://docs.ravenna.ai/api-reference/.
MCP Integration
This server implements the Model Context Protocol (MCP), making it compatible with MCP clients. It exposes tools that can be used by large language models to interact with Ravenna.
Environment Variables
RAVENNA_API_KEY: Your Ravenna API key (required)
Error Handling
All tools include proper error handling and will return appropriate error messages if issues occur. Make sure your Ravenna API key is correctly set up and that you have the necessary permissions to perform operations.
Available Tools
4 toolscreate_ticketB
Create a new ticket in Ravenna
Inputs: title (required), description (required), priority, tags.
get_ticketBRead-onlyIdempotent
Get detailed information about a specific ticket
Inputs: id (required).
list_ticketsARead-onlyIdempotent
List tickets in Ravenna with optional filters
Inputs: status, priority, assignee, tags, +1 more.
update_ticketB
Update an existing ticket in Ravenna
Inputs: id (required), title, description, status, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct ticket action (create, get, list, update) with no overlap.
All tools follow a consistent verb_ticket pattern: create_ticket, get_ticket, list_tickets, update_ticket.
4 tools is a reasonable count for a focused ticket server, covering core operations without being excessive.
Basic CRUD is present but missing delete_ticket, which is a notable gap for ticket management.
Maintenance
Related MCP Connectors
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Helpdesk tickets from your AI: find, reply, take, hold, complete — within your own role. OAuth.
Work your HelpRabbit help desk: tickets, replies, customers, the AI agent and its knowledge.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables managing support tickets from Claude, Cursor, and other AI tools, including listing, creating, updating, and replying to tickets.633 npmMIT- AlicenseAqualityDmaintenanceEnables AI agents to create, query, search, and manage Movidesk tickets directly via natural language.814 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables ticket management and AI triage through Mistral-compatible models, with tools for creating, listing, retrieving, triaging, and updating support tickets.-
- FlicenseNot gradedqualityAmaintenanceEnables retrieving and managing Zendesk tickets and comments, accessing Help Center articles as a knowledge base, and using specialized prompts for ticket analysis and response drafting.-