"Understanding Code Relationships and Dependencies" matching MCP servers:

MCP server enabling AI agents to interact with OpenProject API v3 for project management, including creating and managing work packages, projects, comments, time entries, boards, and user dashboards.

Enables read-only queries across App Store Connect and Google Play from one toolset, letting users list apps, track release states, and review merged store feedback without extra dependencies or credentials in demo mode.

Validates startup ideas with a deterministic scorecard, evidence brief, and verdict before code is written, integrating with MCP-aware build agents to avoid building dead-on-arrival products.

Enables natural language control of OmniPlan 4 on macOS, allowing creation and manipulation of tasks, resources, dependencies, and project metadata through MCP-compatible agents.

MCP server for Tracetify — trace how any product actually grew, without leaving Claude Code or Cursor.

Turns product feedback pinned to a live UI into an actionable backlog for Claude Code — list comments, open one with its target element's HTML, computed styles and screenshot, and update its status.

Connects Huawei AppGallery Connect operational data to any MCP-capable AI client, letting users analyze report trends across 16 report types, crash and AppFreeze metrics, review and rating insights, and generate Markdown daily or weekly digests. All 13 tools are strictly read-only, run with zero dependencies, and keep credentials in memory only.

MCP server for IDEA Base — AI-powered project management. Manage projects, tasks, and time tracking directly from Claude Code, Cursor, or any MCP-compatible AI tool.

MCP server for the Productboard API v2. Provides 30 tools covering entities, notes, relationships, configurations, members, and analytics.

Captures and organizes requirements as markdown, tracks relationships between personas, requirements, use cases, and user stories.

A Model Context Protocol (MCP) server that connects Trello to Claude Code. Manage your boards, lists, cards, checklists, and more — all through natural language.

Enables management of Azure DevOps work items including Epics, Features, User Stories, Tasks, and Bugs through natural language. Supports CRUD operations, WIQL queries, work item relationships, and retrieval of project metadata such as iterations and area paths.

MCP server for GoalT, a multi-parent value-propagating goal graph. It enables building and querying goal trees, listing priorities, and opening a live dashboard that highlights the active goal during Claude Code sessions.

Enables AI assistants to securely access design files, artboards, tokens, PRDs, and design-to-code workflows, letting users implement or match designs from delivery URLs.

Enables AI coding clients to turn code into a linked product specification and run coherence, coverage, and impact checks to surface gaps and contradictions.

Headless MCP server for Simpson Strong-Tie product data. Provides AI agents with structural connector lookups, load calculations, code compliance verification, and engineering specifications.

Enables Claude Code to query a trained sentiment model and Amazon Electronics review analytics through typed, read-only tools. Supports sentiment classification, statistics, keyword and similar-review search, product summaries and comparisons, negative aspect analysis, and model information.

Connects Claude Code, Codex, Cursor, and other coding agents to a project's idea, feature topology, and ordered task queue over MCP, so they can answer planning jobs, claim, build, and tick off implementation tasks live in your repository, or assemble a shareable PRD.

Enables agentic co-authoring of feature specs, decomposition into architecture-validated tickets, and idempotent syncing to Linear as projects with epics, sub-issues, and dependencies.

Turns a rambling app idea into a structured planning canvas of screens, flows, systems, data and open questions inside an existing Claude Code or Codex session, then writes the settled plan back to that session as a spec to build from. Plans are stored in the project's .doan/ folder alongside the code.