zoho-sprint-mcp

MCP (Model Context Protocol) server for fetching Zoho Sprint tickets by ID. Works with Kiro, Claude Desktop, and any MCP-compatible client.

Prerequisites

1. Install the Zoho Sprint VS Code extension
2. Run "Zoho Sprint: Export CLI Config" from the VS Code Command Palette to generate ~/.zoho-sprint.json

Setup

Add this to your MCP config:

Kiro (~/.kiro/settings/mcp.json):

{
  "mcpServers": {
    "zoho-sprint": {
      "command": "npx",
      "args": ["-y", "zoho-sprint-mcp"],
      "env": {},
      "autoApprove": ["get_ticket"]
    }
  }
}

Claude Desktop (claude_desktop_config.json):

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

Available Tools

get_ticket

Fetch a Zoho Sprint ticket by its ID with comprehensive details.

Input:

• ticketId (string, required): The ticket ID, e.g. "42" or "SBO-I301"

Output (all available fields):

• Ticket ID — the item number
• Title — ticket name/summary
• Status — resolved status name (e.g. "In Progress", "Done")
• Priority — resolved priority name (e.g. "High", "Medium", "Low")
• Type — item type name (e.g. "Bug", "Story", "Task")
• Category — derived category (Bug / Feature / HotFix)
• Assignee — display name(s) of assigned team members
• Created By — who created the ticket
• Created / Last Modified — timestamps
• Sprint — sprint name, start date, and end date
• Start Date / End Date — ticket-level dates
• Estimate — estimated effort (formatted as hours/minutes)
• Time Logged — actual time logged
• Duration — total duration
• Parent Item — parent ticket ID (for sub-items)
• Notes — notes/comments info
• Description — full ticket description

How It Works

• Reads OAuth credentials from ~/.zoho-sprint.json
• Automatically refreshes expired access tokens
• Searches the active sprint for the ticket
• Falls back to upcoming sprints if no active sprint exists
• Strips common prefixes (e.g. "SBO-I" from "SBO-I301") for flexible lookup

License

MIT