"A tool for real-time error detection in web browsers" matching MCP servers:

Automates error tracking workflow by finding code owners in Bitbucket, retrieving related pull requests, and creating assigned JIRA tickets for code errors.

Provides tools for logging, confirming, and triaging issues with the semfora-engine, enabling AI agents to report bugs discovered during workflows.

Enables coding agents to discover projects, inspect existing work, atomically claim tasks, record progress, and complete verified work through a task-tracking HTTP API, with version checks, claim coordination, and idempotent retries.

Enables Claude and other MCP clients to log, update, and delete FreshBooks time entries, run and stop timers, and pull summaries of billable and unbilled hours by day, week, client, project, or service, with OAuth-based sign-in and per-user token storage.

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.

Enables tracking work time with start/stop timers, logging entries, and generating reports.

Provides AI assistants with a standardized interface to interact with the Todo for AI task management system. It enables users to retrieve project tasks, create new entries, and submit completion feedback through natural language.

Enables AI assistants to create and manage visual automation configurations, workflows, and UI states through the Qontinui API. It supports project management, workflow execution, and configuration handling for automated web interactions.

Read your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning.

MCP for Azure DevOps Boards is a MCP server that lets your favourite AI browse, query and update Azure DevOps work items as if it were a project manager. Written in Rust and optimized for tokens usagem, It runs via stdio or HTTP mode and uses standard Azure authentication with az login.

Enables interacting with Clockify time-tracking data through natural language, providing tools to manage workspaces, projects, time entries, reports, and more via the MCP protocol.

Enables Codex projects to read Git-backed kickoff, acceptance, handoff, progress, and next-step context, and to append validated, audited progress events through scoped MCP tools. This supports visible agent progress, resumable sessions, and safer handoffs.

Enables Codex and other MCP clients to read kickoff cards, acceptance criteria, Git evidence, and next steps, then append validated, audited progress events for resumable project handoffs.

MCP server for Redmine that enables interaction with issues, wiki pages, and time entries through natural language.

Enables AI-powered project management by connecting Claude to Planka kanban boards via 75+ MCP tools for creating, updating, and managing projects, boards, lists, and cards.

Enables agents to read a project's kickoff card, acceptance criteria, AGENTS rules, handoff package, progress, Git trail, and next step, and to append validated, audited progress events with matching Git commits through short-lived scoped credentials.

Enables AI agents to retrieve Git-backed project context, handoff packages, progress, and next steps, and to append validated progress events with matching project-record commits. This supports visible agent progress, resumable work, and safe handoffs while keeping high-risk actions outside the MCP surface.

Enables agents to read Git-backed project context and append audited, idempotent progress events through scoped, short-lived credentials, supporting resumable handoffs and visible project state.

Enables AI agents and users to verify claims about Jira issues and issue counts against live Jira, retrieve verifiable facts for drafting updates, and re-check previously posted claims. It provides read-only tools and an issue panel so status updates can be evidence-based and mismatches corrected before or after posting.

Enables Codex sessions to read a project's kickoff card, acceptance criteria, handoff package, progress, Git trail, and next step, then append validated, idempotent progress events backed by matching project-record Git commits. Access is limited to a short-lived, revocable credential scoped to one workspace and project, with high-risk actions kept outside the server.