"Resources and Tools for Frontend Development (e.g., Jira, Figma, GitHub)" matching MCP servers:

A Model Context Protocol (MCP) server that enables interaction with JIRA APIs through Claude Desktop, allowing users to search, create, update, and manage JIRA issues using natural language commands.

A Model Context Protocol server that provides access to Figma API functionality, allowing AI assistants like Claude to interact with Figma files, comments, components, and team resources.

A Model Context Protocol server that enables ChatGPT and other AI assistants to directly interact with JIRA issues, currently offering the ability to retrieve issue details.

MCP to Connect JIRA by NodeJs

A simple MCP server that provides access to Jira issues from Cursor AI, allowing users to reference and query Jira tickets directly in the chat panel.

Enables seamless interaction with Figma via the Model Context Protocol, allowing LLM applications to access, manipulate, and track Figma files, components, and variables.

Enables AI assistants to interact with Figma files through the ModelContextProtocol, allowing viewing, commenting, and analyzing Figma designs directly in chat interfaces.

Enables control and interaction with Jira through the Jira Command Line interface, allowing users to manage Jira tasks and operations through natural language commands.

Enables AI assistants to interact with Figma designs programmatically, supporting comprehensive design automation including text manipulation with formatting preservation, batch operations, prototyping, auto-layout configuration, and component management.

Enables AI applications to manage JIRA issues, workflows, and tasks through a standardized MCP interface, facilitating real-time updates and seamless interaction with JIRA's API.

Figma MCP with full API functionality

Provides Jira Cloud integration for AI agents, enabling them to search issues with JQL, retrieve detailed issue information, and create new tickets. It supports multiple Jira configurations and provides tools for managing attachments and comments through natural language.

Enables users to fetch and search Jira tickets, comments, and attachments directly within Claude Code. It features JQL support and automatically exports linked Figma designs to provide comprehensive project context.

Enables AI assistants to read Figma design files and automatically map responsive relationships between mobile and desktop screens to generate accurate frontend code. Eliminates manual copy-pasting by providing direct access to design tokens, dimensions, and screen layouts within AI-powered IDEs.

Enables headless Jira Cloud automation via MCP: create issues and subtasks, read and JQL-search issues, inspect agile boards and swimlanes, move issues through workflows, and add comments and attachments.

Enables AI assistants like Cursor to interact with Figma designs programmatically. Supports reading design information, modifying elements, creating components, managing text content, and automating design workflows through natural language commands.

Connects AI applications to Figma API for extracting design data, generating production-ready HTML/CSS from designs, and capturing screenshots in multiple formats.

A server implementation that enables interaction with Figma API through Model Context Protocol (MCP), supporting plugin and widget development with WebSocket communication capabilities.

Figma MCP Bridge is a combined Figma plugin and MCP server that bypasses Figma's free API rate limits by streaming live document data directly to AI tools via a local WebSocket connection instead of the standard cloud API.

Enables enterprise-level integration with Jira's REST API for AI assistants to perform advanced project management, issue tracking, analytics, and strategic planning tasks. Supports multiple Jira instances with thread-safe concurrent access, workflow management, and comprehensive project structure organization.

A Model Context Protocol server that connects AI tools and LLMs to Figma designs, enabling them to extract design data, analyze design systems, and generate development documentation.

Enables AI assistants to access locally installed fonts and control Figma text through a local bridge, including listing, auditing, replacing, and setting fonts on text nodes.

A production-ready server that automatically exposes your entire Jira instance through the Model Context Protocol, allowing seamless interaction with Jira's API features including issue management, project administration, and user management.

Enables agents to subscribe to comments in selected Figma files, pages, frames, folders, teams, or organizations, optionally filtered by tag, and retrieve new comment events over MCP stdio. It polls Figma's REST API locally so the receiving agent can decide how to react.

Enables AI assistants to manage Jira Cloud instances, including creating and updating issues, managing sprints and projects, adding comments, tracking worklogs, and searching with presets.

Connects an MCP client such as Claude Code to the Figma file open in the desktop app, letting the agent create frames, write text, apply styles, import images and SVGs, take screenshots, and run arbitrary Figma Plugin API code. Commands travel through a local development plugin instead of Figma's web API, so there are no tokens, quotas, or rate limits.

Enables AI assistants to search, view, create, and update JIRA issues using natural language commands and JQL queries.

Enables AI agents to create, modify, and manage Figma designs through natural language commands via a specialized MCP server and plugin bridge. It supports a wide range of operations including element creation, property modification, component management, and accessibility checks.

Brings Figma designs directly into MCP-compatible environments to view specifications and export frames as high-resolution images. It features smart section splitting for large frames and integrates with Jira to automatically fetch designs from ticket links.

Provides Dify apps with a secure, app-scoped MCP tool catalog and action gateway for authorized FlowFlox operations, enabling intent-driven planning and fixed operational processes without exposing global credentials.