"User Interface Design or Information" matching MCP servers:

Simple MCP Server to enable a human-in-the-loop workflow in tools like Cline and Cursor. This is especially useful for developing desktop applications that require complex user interactions to test.

MCP server bridging ChatGPT-compatible clients to the Design Flow System, enabling project session management, draft import, round locking, and read-only access to design state and traceability.

Enables the creation and management of business design artifacts including Business Model Canvases, SWOT analyses, and user personas. It features project organization and AI-powered research tools to automatically populate frameworks with market data.

Enables ZenTao user administration, including token retrieval, user queries, and user creation/update/delete, over stdio or Streamable HTTP transports.

Turns live meeting utterances into work while people talk, producing plan, design, verification, and research cards plus stored decisions, action items, and workspace files. Small writes land immediately, while scaffolding, test runs, issue creation, and pull requests wait for an explicit yes, and stop/不对 roll back a checkpoint.

Enables Claude Desktop to add and edit ConstructionClock time entries directly through the ConstructionClock REST API.

Enables AI assistants to interact with CA Clarity PPM for discovery, CRUD operations, and analytics.

Enables AI assistants to interact with Fergus job management platform through secure API integration. Supports managing jobs, customers, quotes, and sites with real-time data synchronization.

An MCP server for AI assistants to create and manage SAP Solution Manager Focused Build Requirements and navigate the Solution Documentation process hierarchy via SAP OData API.

Enables specification-driven development workflows for AI editors by managing structured project specifications through stages like requirements, design, and tasks.

Enables AI coding tools to follow a structured spec-driven development workflow with three phases: requirements, design, and tasks, ensuring approval before advancing.

Enables Claude to interact with LifeUp Cloud API on your local network for task management, achievements, and user information. Supports 20 tools including creating, editing, and querying tasks, achievements, and shop items.

Enables MCP clients to interact with Zammad tickets, articles, search and replies under each caller's own permissions, using either a static token or SSO/OIDC per-user mode.

Enables VS Code Copilot to interact with your Jira instance—Cloud, Server, or Data Center—through natural language for issue search, creation, updates, comments, transitions, assignments, project listing, and user profile lookup.

Enables interaction with self-hosted Jira instances using Personal Access Token authentication, letting users create, read, update, delete, and transition issues, search with JQL, and manage comments, assignments, projects, and issue types. Also supports fetching the current user's information and configuring custom fields and User-Agent headers for reverse-proxy setups.

This is an unofficial, community-built MCP server for qTest Manager. Not affiliated with or endorsed by Tricentis. Browse projects, modules, and test cases Create/delete test design modules Create and manage test execution cycles Add test cases into execution suites

Enables defect management on the SEPP platform, allowing users to query defects, retrieve user project information, and set up automated monitoring with alerts for new or unresolved defects via webhook or email.

A secure Model Context Protocol server for interacting with the WorkBoard OKR and strategy execution platform. It enables users to manage user profiles and track goal progress through a standardized, containerized interface.

Enables interaction with the Runrun.it API for task management, including retrieving task details, listing tasks with filters, and fetching current user information.

Enables any MCP-capable coding agent to gate code writing behind user-approved design checkpoints, asking for the user's own approach first and recording decisions, project maps, and progress in a local .vibe-wise/ folder. Code is only written once the user explicitly confirms an implementation checkpoint, with no account, backend, or telemetry required.