Povio Worklog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POVIO_API_TOKEN | Yes | Your Povio dashboard cookie token value. Just provide the token value - the _poviolabs_dashboard= prefix is automatically added. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_povio_projectsA | List all active projects assigned to you in Povio. Shows project names and IDs for easy reference when posting worklogs. Trigger examples:
|
| generate_worklogA | Generate a worklog from git commits. Analyzes commit messages, extracts ticket numbers, and creates AI-enhanced, professional worklog descriptions following Povio guidelines. AI enhancement is ENABLED BY DEFAULT. Supported date formats:
Trigger examples:
|
| post_worklogA | Post a worklog entry to Povio dashboard. Supports both project ID and project name. Uses DEFAULT_PROJECT_ID from environment if neither is provided. Trigger examples:
|
| generate_and_post_worklogA | Generate worklog from git commits AND post it to Povio in one step. Supports both project ID and project name. AI enhancement is ENABLED BY DEFAULT - generation will pause for AI to create an enhanced description before posting. Supported date formats:
Trigger examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| wl | Quick worklog generation from git commits. Generate for today, yesterday, or a specific date. Optionally specify project and hours to generate and post in one step. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: listing projects, generating worklog content, posting a worklog, and combining generation with posting. The differences are explicitly stated, and the compound tool is self-descriptive.
All tool names follow a snake_case verb_object pattern (list_*, generate_*, post_*, generate_and_post_*), making the action and target predictable. The inclusion of 'povio' in list_povio_projects is a minor contextual addition but does not break the pattern.
With only 4 tools, the server is well-scoped for its purpose: supporting a focused workflow of project lookup, worklog generation, posting, and a combined convenience operation. No unnecessary extras or missing core functions.
The set fully covers creating and submitting worklogs, but it lacks any ability to read, update, or delete existing worklogs, which could be a dead end for agents needing to verify submissions or fix mistakes. This is a notable gap for a worklog management server.