Povio Worklog

Provides AI-enhanced worklog generation from git commits and posts to Povio via MCP.

typescript

2

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months 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": {
    "egzonarifi-povio-worklog-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "povio-worklog-mcp"
      ],
      "env": {
        "POVIO_API_TOKEN": "your-povio-token-value"
      }
    }
  }
}

You have a Povio Worklog MCP Server that automatically analyzes your git commits and generates client-ready worklog descriptions, with optional AI enhancement and direct posting to the Povio dashboard. This MCP server streamlines the process from committing code to creating polished worklogs and attaching them to projects in Povio.

How to use

You interact with the server through a client that supports MCP commands. Start by listing your Povio projects to understand what you can post to, then generate worklogs for a chosen date or timeframe, and optionally post them to a project in Povio. The AI-enhanced generator produces professional descriptions aligned with Povio guidelines, and you can combine generation and posting in a single step.

How to install

Prerequisites: you need Node.js and npm installed on your machine. You also work with a Cursor MCP client to load and run the MCP server.

Install and configure the MCP server in Cursor by creating or editing the MCP configuration file at the following path.

{
  "mcpServers": {
    "povio-worklog": {
      "command": "npx",
      "args": ["-y", "povio-worklog-mcp"],
      "env": {
        "POVIO_API_TOKEN": "your-povio-token-value"
      }
    }
  }
}

Configuration and usage notes

Set a token value for POVIO_API_TOKEN. You provide only the token value itself; Cursor automatically prefixes it as needed.

The MCP server uses the current working directory of your Cursor workspace as the git repository for worklog generation.

If you need to develop or customize the MCP server locally, you can install dependencies, build, and run a local instance. The typical flow is to install, build, and run the server, then configure Cursor to point at the local runtime.

Usage patterns and commands

List your Povio projects to understand available targets.

Generate a worklog for today or a specific date, optionally tailoring the description with AI, and post to a project.

Generate and post in a single step when you want to create the worklog description and publish it directly to Povio.

Available tools and capabilities

The MCP server exposes the following primary tools to help manage worklogs:

list_povio_projects — List all active Povio projects with their names and roles, so you can target the correct project when posting.
generate_worklog — Create a worklog description from git commits, with optional AI enhancement and support for various date formats.
post_worklog — Post a generated worklog description to Povio for a specified project, hours, and date.
generate_and_post_worklog — Generate a worklog from commits and post it to Povio in one step, with options to specify project and date.

Available tools

list_povio_projects

List all active Povio projects with their IDs and roles.

generate_worklog

Create a worklog description from git commits for a given timeframe and repository, with optional AI enhancement.

post_worklog

Post a generated worklog to a Povio project with a specified date and hours.

generate_and_post_worklog

Generate a worklog from commits and post it to Povio in a single step, with optional AI enhancement.