7pace Timetracker

AI-powered MCP server that logs time to Azure DevOps via natural language in Claude AI.
  • javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 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": {
    "turnono-7pace-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "github:turnono/7pace-mcp-server"
      ],
      "env": {
        "SEVENPACE_TOKEN": "your-token",
        "SEVENPACE_ORGANIZATION": "your-org"
      }
    }
  }
}

You can supercharge your Azure DevOps workflow with an MCP server that lets you log and manage time using natural language directly from Claude AI. This server voicefully links time entries to work items and provides real-time sync, smart reports, and a smooth developer experience without leaving your coding environment.

How to use

You interact with the 7pace Timetracker MCP Server through your MCP client by sending natural language time tracking requests. Speak or type commands such as logging hours against a specific work item, then review, edit, or generate reports from the time data. Use it to power sprint reviews, client billing, and productivity analyses. The server resolves activity types automatically when you provide a name or ID and keeps your Azure DevOps data in sync in real time.

How to install

Prerequisites: ensure you have Node.js and npm installed on your machine. You may also want Git for cloning repositories. If you plan to run in a development mode, you will use npm commands directly from the project folder.

Step 1: Clone the project repository.

Step 2: Install dependencies.

Step 3: Build the project.

Step 4: Run the server in development mode or start it for production.

Configuration and usage notes

{
  "mcpServers": {
    "7pace-timetracker": {
      "command": "npx",
      "args": ["-y", "github:turnono/7pace-mcp-server"],
      "env": {
        "SEVENPACE_ORGANIZATION": "your-org",
        "SEVENPACE_TOKEN": "your-token"
      }
    }
  }
}

For Cursor IDE configuration, place the MCP server entry under mcpServers with the provided command and environment variables. For VS Code, create a .vscode/mcp.json file with the stdio configuration that points to the same MCP server and includes your environment variables.

Examples and expectations

Natural language time tracking, smart reports, and intelligent queries translate into actionable Azure DevOps data. You can ask the assistant to log hours, list or filter worklogs, and generate time reports for a chosen date range or user.

API reference at a glance

You interact with the MCP server through high-level functions like log_time, get_worklogs, list_activity_types, update_worklog, delete_worklog, and generate_time_report. The server coordinates with the 7pace API and Azure DevOps to create accurate work logs, retrieve entries, resolve activity types, and produce reports.

Security and access

Keep your API token and organization identifier secure. Store them in environment variables, and restrict access to your development and production environments. Use token-based authentication and isolate your MCP server processes to minimize risk.

Notes and troubleshooting

If you run into connectivity issues, verify your SEVENPACE_ORGANIZATION and SEVENPACE_TOKEN values, confirm your Azure DevOps URLs and PAT if used, and ensure your environment timeout settings accommodate your network. Restart your MCP server after changing environment variables.

Additional configuration examples

{
  "servers": {
    "7pace-timetracker": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "github:turnono/7pace-mcp-server"],
      "env": {
        "SEVENPACE_ORGANIZATION": "your-org",
        "SEVENPACE_TOKEN": "your-token"
      }
    }
  }
}

Troubleshooting common issues

If the server doesn’t start, double-check that the command and arguments exactly match the provided configuration snippets, and ensure the environment variables are set. Look for clear error messages about missing tokens or invalid work item IDs and adjust your configuration accordingly.

Available tools

log_time

Logs a time entry for a specified work item with date, hours, description, and optional activity type.

get_worklogs

Retrieves time entries with optional filters such as work item, start date, and end date.

list_activity_types

Returns a list of available activity types to map names to IDs.

update_worklog

Updates an existing time entry by worklogId with new hours, description, or work item.

delete_worklog

Deletes a specified time entry by its worklogId.

generate_time_report

Generates a time tracking report for a given date range and optional user filter.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational