mcp-intervals

MCP server for Intervals task management. Lets Claude read and update tasks, add notes, and browse projects and milestones directly from your Intervals account.

Quick Start

Run the interactive installer:

npx mcp-intervals init

This will:

1. Detect your shell (zsh, bash, or PowerShell)
2. Store your API token securely in your shell profile (not in config files)
3. Detect installed MCP clients (Claude Code, Claude Desktop, Cursor, Windsurf)
4. Configure the selected clients

Security

The installer stores your API token as an environment variable in your shell profile (~/.zshrc, ~/.bashrc, or PowerShell profile), keeping it out of project files that might be committed to git. MCP config files only contain the command reference, not the token.

Manual Setup

1. Get your Intervals API token

1. Log in to your Intervals account
2. Go to Options (bottom-left) > My Account > API Access
3. Copy your API token

2. Add the token to your shell profile

Add the following line to your shell profile:

macOS/Linux (zsh) - Add to ~/.zshrc:

export INTERVALS_API_TOKEN="YOUR_TOKEN"

macOS/Linux (bash) - Add to ~/.bashrc or ~/.bash_profile:

export INTERVALS_API_TOKEN="YOUR_TOKEN"

Windows (PowerShell) - Add to your PowerShell profile:

$env:INTERVALS_API_TOKEN = "YOUR_TOKEN"

Then reload your shell or restart your terminal.

3. Configure MCP clients

Add this to your MCP config file (token is read from environment):

Claude Code:

claude mcp add intervals --scope user -- npx -y mcp-intervals

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "intervals": {
      "command": "npx",
      "args": ["-y", "mcp-intervals"]
    }
  }
}

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "intervals": {
      "command": "npx",
      "args": ["-y", "mcp-intervals"]
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "intervals": {
      "command": "npx",
      "args": ["-y", "mcp-intervals"]
    }
  }
}

Available Tools

| Tool | Description | | ------------------ | ---------------------------------------------------------------------------- | | get_task | Get task details by local ID or Intervals URL | | update_task | Update task status, assignee, priority, title, description, due date, owner | | add_task_note | Add a comment/note to a task (supports HTML) | | get_task_notes | Retrieve all comments/notes on a task | | add_time_entry | Add a time entry to a task (billable/unbillable with work type) | | get_time_entries | Retrieve time entries (filter by task, date range) | | get_project | Get project details (name, client, dates, budget) | | get_milestone | Get milestone details (title, due date, progress) |

Resources

| Resource | URI | Description | | --------------- | ------------------------ | ----------------------------------------------------- | | Task Statuses | intervals://statuses | List of all status IDs for use with update_task | | Task Priorities | intervals://priorities | List of all priority IDs for use with update_task | | Work Types | intervals://worktypes | List of all work type IDs for use with time entries |

Example Usage

Once installed, you can ask Claude things like:

• "Get the details of task 1234"
• "Update task 1234 status to closed"
• "Update the description of task 1234 to explain the new requirements"
• "Add a note to task 1234 saying the fix has been deployed"
• "Show me all notes on task 1234"
• "Log 2 hours of billable time on task 1234 for today"
• "Add 30 minutes of unbillable time to task 1234 for code review"
• "Show me all time entries for task 1234"
• "What are the details of project 5?"

License

MIT