REI3-Tickets

This MCP server provides integration with the REI3 Tickets system, exposing ticket creation, worklog entry creation, and retrieval of ticket information through the MCP protocol. It supports transport via HTTP by default, and can be consumed by MCP clients that understand the streamable MCP format. You can also run it in stdio mode using uv, which enables direct script execution with a local directory reference. To use the server, point your MCP client (or AnythingLLM/other MCP-enabled client) to the server's endpoint and select the transport mode you prefer. For HTTP transport, you typically configure the server URL (for example, http://127.0.0.1:54321/mcp/) and use a streamable connection; for stdio transport, provide the Python script path and directory via uv so the client can invoke the server process directly. The README also documents an mcp-remote option via npx for OAuth-free setups if your client lacks native OAuth support.

Prerequisites:

• Python 3.13.5
• uv (Python package manager) installed and added to PATH
• A designated REI3 user with Tickets API access
• An API Profile configured in your REI3 Tickets instance
• Access to the REI3 Tickets MCP Server repository (downloaded/cloned)

Installation steps:

1. Install Python 3.13.5 from the official source.
2. Install uv: python -m pip install uv
3. Add Python and uv to your system PATH so commands can be run from any directory.
4. Create a dedicated REI3 user with Tickets API access and set up an API Profile under Tickets > Admin Tab > API profiles.
5. Download or clone the REI3-Tickets-MCP-Server repository and adjust the config.ini with your environment values (API credentials, endpoints, etc.).
6. Ensure you have an MCP Client capable of running MCP tools (examples include AnythingLLM).
7. Configure the MCP-Server JSON configuration to reference the REI3-Tickets-MCP-Server (see example in the repository README).
8. Run the server using the chosen transport (HTTP or stdio) per your environment and MCP client capabilities.

Notes and tips:

• The README provides multiple transport configurations (HTTP, stdio) and an mcp-remote option for OAuth flows. If your client does not support OAuth, consider the mcp-remote approach at https://www.npmjs.com/package/mcp-remote.
• If using the HTTP transport, ensure the server URL (e.g., http://127.0.0.1:54321/mcp/) is accessible from your MCP client.
• The stdio transport uses uv with a directory path; ensure the ABSOLUTE path points to the parent folder containing the REI3-Tickets-MCP-Server-main directory and that rei3_tickets_mcp_server.py exists there.
• Be aware of potential issues with FastMCP disk storage backends blocking new releases, as noted in the README. If you encounter build issues, use alternative installation methods (Python/uv or docker).
• If you plan to run via Docker, follow the Docker-specific installation steps and use the provided setup_docker.ps1 to create the image and container.