# 7Pace-Connector

An MCP (Model Context Protocol) server that connects Claude to the [7pace Timetracker](https://www.7pace.com/) API for Jira.

## Tools

| Tool | Description |
|------|-------------|
| `list_worklogs` | List work logs, filter by assignee or Jira issue, cursor-paginate |
| `get_worklog` | Get all logs for a Jira issue with total time summary |
| `log_time` | Create a new time entry (duration in minutes) |
| `update_worklog` | Update an existing entry by UUID |
| `delete_worklog` | Delete an entry by UUID |
| `summarize_time` | Paginate all logs and show total + breakdown by Jira issue |

## Setup

### 1. Install dependencies and build

```bash
npm install
npm run build
```

### 2. Generate a 7pace API token

In 7pace → Settings → API Tokens → generate a new token.

### 3. Register in Claude Code

Add to your `~/.claude/mcp.json`:

```json
{
  "mcpServers": {
    "7Pace-Connector": {
      "command": "node",
      "args": ["/path/to/TimeReporting/dist/index.js"],
      "env": {
        "SEVENPACE_TOKEN": "your-token-here"
      }
    }
  }
}
```

Restart Claude Code. The MCP server will connect automatically.

## API Details

- **Base URL:** `https://timehubjra.7pace.com/api/v1`
- **Auth:** Bearer token via `SEVENPACE_TOKEN` env var
- **Pagination:** cursor-based via `pageInfo.endCursor`
- **Filter params:** `assigneeId`, `externalItemId`, `after` (cursor)

## Notes

- `externalItemId` is the **numeric** Jira issue ID (not the key like `PROJ-123`)
- `duration` is in seconds; all tools accept/display minutes for convenience
- Your token stays in your local `~/.claude/mcp.json` and is never committed