Ravenna MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAVENNA_API_KEY | Yes | Your Ravenna API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_ticketB | Create a new ticket in Ravenna |
| update_ticketB | Update an existing ticket in Ravenna |
| list_ticketsA | List tickets in Ravenna with optional filters |
| get_ticketB | Get detailed information about a specific ticket |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.