REI3 Tickets

You can run the REI3 Tickets MCP Server to expose a lightweight MCP endpoint that lets clients create tickets, add worklog entries, close tickets by key, and fetch ticket context and information. This server integrates with REI3 Tickets and provides practical MCP access for automation, tooling, and integrations.

How to use

To operate with an MCP client, point the client at the HTTP MCP endpoint first. If you prefer a local process, you can run an MCP client that connects via a stdio-based launcher. The server exposes core capabilities such as creating tickets, attaching worklog entries, closing tickets by key, and retrieving ticket details by key.

Typical usage patterns include: creating a new ticket, logging work against an existing ticket, retrieving the current status or context of a ticket, and querying ticket details by its key. Your MCP client will issue requests that map to these actions, and the server will respond with the resulting ticket data or confirmations of actions taken.

If you plan to run the server locally, ensure your MCP client can reach the HTTP endpoint at the configured URL. If you are using a local stdio setup, start the launcher that invokes the REI3 Tickets MCP Server process and monitor the output for startup success.

How to install

Prerequisites depend on the installation method you choose. Prepare your environment before starting the server.

Release (prebuilt) installation steps

• Create a designated user in REI3 with access to the Tickets API role. This user will be used for authentication.

• Set up an API Profile in your REI3 Tickets instance under Tickets > Admin Tab > API profiles.

• Download the latest release of the MCP Server.

• Set-ExecutionPolicy Bypass if you plan to run the provided open_config.ps1 script.

• Adjust config.ini with the appropriate variables for your environment.

• Start the REI3 Tickets MCP Server executable, for example REI3 Tickets MCP Server.exe.

Manual installation steps

• Install Python 3.13.5.

• Install the uv Python package manager and add uv to your PATH.

• Create a designated user in REI3 with access to the Tickets API role.

• Set up an API Profile in your REI3 Tickets instance under Tickets > Admin Tab > API profiles.

• Download or clone and extract the MCP server repository and adjust the config.ini file variables.

• Ensure you have an MCP Client capable of running MCP tools. Example clients include AnythingLLM.

• Configure the MCP-Server JSON configuration to include the REI3-Tickets-MCP-Server.

Docker installation steps

• Install Docker.

• Install Git.

• Create a designated user in REI3 with access to the Tickets API role.

• Set up an API Profile in your REI3 Tickets instance.

• Download or clone and extract the MCP server repository and adjust the config.ini file variables.

• Run the setup_docker.ps1 script to build the Docker image and to get container creation instructions.

Additional configuration and notes

HTTP transport configuration is provided for remote MCP connectivity. You can reach the MCP server at the following URL when using an HTTP transport: http://127.0.0.1:54321/mcp/.

If you need an alternative client-side approach, you can use the mcp-remote package to connect via HTTP. Example usage starts with a command that launches mcp-remote against your MCP URL.

Security note: use a dedicated REI3 user with precise API access for MCP interactions. Keep API credentials secure and rotate them as needed.

Important compatibility note: the stdio transport option has been removed in newer versions. Favor the HTTP transport method for MCP connectivity.

Examples of server endpoints and transport methods

{
  "mcpServers": {
	"rei3_tickets_http" : {
		"url": "http://127.0.0.1:54321/mcp/",
		"type": "http",
		"args": []
	}
  }
}

{
  "mcpServers": {
	"rei3_tickets_remote" : {
		"command": "npx",
		"args": [
          "mcp-remote",
          "https://127.0.0.1:54321/mcp/"
        ]
	}
  }
}

Troubleshooting tips

If the server fails to start, check the config.ini values for correctness, ensure the REI3 Tickets API is reachable with the credentials you created, and verify that the MCP client configuration references the correct MCP URL.

Available tools

Create ticket

Create a new ticket in REI3 Tickets with the provided details.

Create ticket worklog

Add a worklog entry to an existing ticket to record progress or updates.

Close ticket by key

Close a ticket using its unique ticket key to mark it as resolved.

Get ticket context

Retrieve contextual information related to a ticket by its key.

Get ticket info

Fetch full ticket details by key for review or processing.