"Pivotal Tracker" matching MCP servers:

Enables AI assistants to securely interact with Yandex Tracker, managing issues, queues, comments, worklogs, and search, including attaching files to issues.

This MCP enables access to Yandex Tracker issue management. Currently it supports all read operations to retrieve queues, issues and users from Yandex Tracker.

Enables secure interaction with Request Tracker (RT) for ticket management, including search, creation, updates, resolution, time tracking, and workflow automation.

MCP server for Yandex Tracker API that provides 146 tools for managing issues, projects, boards, sprints, worklog and more.

MCP server for Yandex Tracker API, enabling AI assistants to search, read, create, and edit issues, as well as manage comments, attachments, and links in Yandex Tracker.

Enables read-only MCP access to Yandex Tracker for retrieving issues with comments and attachment metadata, searching issues, reading issue history, downloading attachments, and finding users. It also supports connection status checks and token configuration without exposing secrets.

Enables interaction with a local SQLite-backed issue tracker, offering full CRUD operations (search, fetch, summarize, create, comment, close/reopen) with team-scoped visibility, authorization, rate limiting, and audit logging.

A Node.js MCP server that enables AI assistants to interact with Yandex Tracker task management system through a standardized protocol, supporting operations like creating, updating, and searching issues.

Enables LLM clients to interact with a local tracker-server for checking schedule, retrieving statistics, registering tasks, and managing timers.

Enables AI agents to manage job applications, documents, and contacts via the Application Tracker workspace, with read-only or write access controlled by administrator settings.

Enables AI agents to manage a personal job application tracker, allowing users to list, add, update, and delete job applications with company, role, and status details through natural language.

A local MCP server that reads logged hours from an internal time tracker, providing tools to list time entries, projects, and the active timer. It is read-only, enabling Claude Code to see time-tracking data without writing.

An MCP server that exposes the markdown issue tracker under .scratch/ as a queryable graph, letting agents see open, blocked, or takeable issues without re-parsing prose.

Job application tracker for developers: AI agents write over a remote MCP server (OAuth), humans review in a dashboard at jobctl app.

A MCP server for interacting with FogBugz issue tracker through LLMs such as Claude. Supports both the XML API (/api.asp) and the JSON API (/f/api/0/jsonapi) with automatic version detection at startup. Works with on-premise and on-demand FogBugz installations.

An unofficial MCP server that enables AI assistants to work with Yandex Tracker, Yandex Mail, and Yandex Calendar on the user's behalf, supporting reading, writing, and workflow automations such as meeting follow-ups, standups, and email-to-task creation.

Read-only MCP server for Request Tracker (RT) via REST2 API, enabling ticket search, retrieval, correspondence viewing, attachment download, and hierarchy exploration.

MCP server that enables managing tasks (Activities) in a Kimai project and tracking time, with tools to list, create, complete, reopen, start/stop timers, and log time.

Exposes Yandex Tracker's REST API v3 as tools for LLM clients, enabling issue management and queue operations via natural language.

Enables AI agents to query Firefox's Bugzilla tracker for bugs, comments, history, attachments, dependency/duplicate graphs, and product/component/field metadata. It is read-only and works without credentials for public bugs, with an optional API key for private bugs and user lookups.