Gorev

Provides a multi-client MCP server for task management with an embedded UI and REST API.

go

1

GitHub Stars

go

Language

3 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "msenol-gorev": {
      "command": "npx",
      "args": [
        "-y",
        "@mehmetsenol/gorev-mcp-server@latest"
      ],
      "env": {
        "GOREV_LANG": "en"
      }
    }
  }
}

Gorev MCP Server is a Go-based back-end that enables multi-client task management through the Model Context Protocol (MCP). It supports connections from MCP-compatible editors and assistants, provides a REST API and an embedded web UI, and runs as a background daemon to coordinate tasks, projects, and workflows across multiple clients.

How to use

Install and run Gorev to start coordinating tasks with MCP-compatible editors. You will connect your editor or AI assistant to Gorev, and the system will manage tasks, projects, templates, subtasks, and real-time updates through a unified interface.

Start the Gorev daemon in the background so it can service MCP clients. Then connect your MCP-enabled editor or assistant to the Gorev endpoint. Use the built-in Web UI for an overview and management if you prefer a visual interface.

How to install

Prerequisites: ensure you have Node.js and npm installed on your system.

Install Gorev via NPX for immediate use.
Start Gorev in the background using the daemon command so it runs as a persistent service.
Connect your MCP client to Gorev and begin task management.
Access the embedded Web UI at the default URL once the daemon is running.

Configuration and usage notes

The Gorev setup includes a standard MCP server configuration that is designed to be used with MCP-compatible editors. The recommended way to run is via npx so you pull the latest server binary and start the daemon for MCP integration.

Troubleshooting and tips

If the daemon cannot start or a client cannot connect, verify that the daemon is running in the background and that the correct MCP client configuration points to Gorev. Use the health endpoint to check status and confirm real-time updates are flowing to connected clients.

MCP client configuration example

{
  "mcpServers": {
    "gorev": {
      "command": "npx",
      "args": [
        "-y",
        "@mehmetsenol/gorev-mcp-server@latest"
      ],
      "env": {
        "GOREV_LANG": "en"
      }
    }
  }
}

Project structure and components

Gorev operates as a daemon that serves MCP clients via a proxy and REST API, with an embedded Web UI for quick task management. A lock file prevents port conflicts, and a SQLite database stores task and workspace data.

Available tools

gorev_bulk

Bulk operations for updating tasks, including transforming updates into a unified format for multiple tasks.

gorev_guncelle

Update multiple fields on a task, such as status and priority, with validation for at least one parameter.

gorev_search

Advanced search with smart language parsing to extract filters from natural language queries.