This MCP server provides an interface to manage Ravenna tickets through a standard MCP-enabled client. It exposes tools for creating tickets, updating existing tickets, listing tickets with filters, and retrieving detailed information about a specific ticket. The Create Ticket tool accepts a title and description as required fields, with optional priority and tags to categorize the ticket. The Update Ticket tool requires the ticket id and supports updating fields like title, description, status, priority, assignee, and tags. The List Tickets tool lets you filter by status, priority, assignee, and tags, and supports limiting the number of results. The Get Ticket tool returns full details for a specified ticket by id. You’ll interact with these tools via the MCP protocol, sending JSON payloads to perform the corresponding Ravenna operations.

Prerequisites:

• Node.js (recommended LTS) and npm or bun installed on your machine.
• Access to Ravenna API with a valid API key.

Install and run locally:

1. Clone the repository: git clone https://github.com/your-org/ravennahq-ravenna-mcp-server.git cd ravennahq-ravenna-mcp-server

2. Install dependencies: npm install

   or

   bun install

3. Set the Ravenna API key in the environment: export RAVENNA_API_KEY=your_api_key_here

4. Start the server (stdio MCP compatible): bun run index.ts

   or

   npm run start

Note: The MCP server is designed to run over stdio for compatibility with MCP clients such as Claude Desktop and other MCP-enabled applications.

Environment variable RAVENNA_API_KEY is required for all operations. If you encounter authentication errors, double-check that the API key is valid and has the necessary permissions in Ravenna. The server exposes typical ticket operations (create, update, list, get); ensure you provide required fields (e.g., title and description for create, id for get/update). When listing tickets, you can combine filters like status, priority, and tags to narrow results. If you deploy in a containerized environment, pass the RAVENNA_API_KEY as an environment variable in your container runtime. The MCP server logs are helpful for debugging; watch for errors related to API calls or invalid payload structures.