"Troubleshooting Frontend Webpage Errors" matching MCP servers:

A schema-aware MCP server for Redmine that validates issue writes against workflow graphs and custom field schemas to prevent errors, with tools for issue lifecycle, time tracking, wiki pages, and more.

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

A reusable AI software development team built on MCP. 13 specialized agents (Project Manager, Backend, Frontend, QA, Security, DevOps, UX, and more) collaborate via shared SQLite state. Exposes 44 MCP tools across 12 domains. All discussions and decisions are stored in the database so agents get back up to speed immediately when re-loaded.

Enables filtered, read-only querying of a Notion audit trail and action queue as four native tools (filtered lists and single-row lookups), with enum parameters validated against the live database schema and errors that report allowed values. It never writes to Notion, returns flat JSON rows, and keeps the integration token server-side.

An MCP server for managing tickets and meetings with CRUD operations, backed by PostgreSQL, and includes a REST API and React frontend.

Enables intelligent analysis of regression test failures and automatic discovery of solutions in JIRA. Analyzes test logs using AI-driven algorithms and matches errors with relevant JIRA issues through natural language interactions.

A self-hosted synchronization hub for frontend and backend teams using Cursor, enabling publishing and reading of shared project state with a local React dashboard.

Enables AI clients to list, retrieve, create, update, and delete tracked issues through MCP tools that call an underlying FastAPI REST API over HTTP. Issue status and priority values are validated, and API or network failures surface as MCP tool errors.