Skip to main content
Glama
72,476 servers. Updated

Matching MCP tools:

Matching MCP Connectors:

"Servers for Searching Recently Updated Jira Issues" matching MCP servers:

  • gh-issues-mcp

    joachimwedin
    A
    license
    -
    quality
    B
    maintenance
    A standalone MCP server that exposes a narrow set of GitHub Issues tools for a single repository, securely handling a GitHub personal access token so agents never see the credential.
    MIT

  • mcp-jira

    judexzhu
    F
    license
    A
    quality
    C
    maintenance
    An async MCP server for JIRA integration, enabling AI assistants to search, create, and manage JIRA issues via JQL and other operations.
    6
    1

  • mcp-servers (Six production

    prathamesh-git9
    A
    license
    B
    quality
    B
    maintenance
    A workspace of six MCP servers—grounded-cv (hybrid RAG with citations), repo-intel (GitHub repo intelligence), web-research (safe web search/extraction), ats-jobs (unified ATS job boards), outcome-ledger (durable task ledger), and coding-workflows (code review & planning)—purpose-built for agentic hiring evaluations.
    2
    MIT

  • jira-mcp-server

    thisIsRasel
    A
    license
    B
    quality
    C
    maintenance
    Stdio-based MCP server exposing Jira tools for searching, creating, getting, commenting on, assigning, and transitioning issues, as well as listing projects, with authentication via token or basic auth.
    7
    55
    Apache 2.0

  • mcp-jira

    sweco-beb283
    A
    license
    -
    quality
    C
    maintenance
    A local MCP server for safely managing personal Jira Cloud issues through ACLI, reusing an existing OAuth session without storing credentials. It enables listing, searching, and reading assigned issues, ranking potential duplicates, and making confirmed updates like comments, transitions, and field changes.
    53
    MIT

  • Jira MCP Server

    Eliya-56
    A
    license
    -
    quality
    D
    maintenance
    Enables AI assistants to manage Jira issues with full CRUD, transitions, linking, commenting, and file attachments via the Jira REST API v3.
    55
    Apache 2.0

  • jira-pilot

    Aarul5
    A
    license
    -
    quality
    C
    maintenance
    Jira Pilot is an MCP server that provides 14 tools for AI assistants to manage Jira issues, sprints, boards, and more. It enables natural language interaction with Jira through the Model Context Protocol.
    33
    4
    ISC

  • jira-mcp

    Pandacli
    A
    license
    -
    quality
    C
    maintenance
    A lightweight MCP server for self-hosted Jira Server, exposing REST API v2 tools for search, issue creation/update, transitions, comments, and more to AI clients via MCP protocol.
    MIT

  • mcp-file-servers

    ChniaPxs
    F
    license
    -
    quality
    C
    maintenance
    Enables file operations (PDF, Office, images, archives, media) through natural language, with tools for reading, writing, converting, and analyzing files locally.
    1

  • Jira MCP

    southocean
    F
    license
    -
    quality
    A
    maintenance
    A one-click Jira integration for AI coding tools like Claude Desktop, Cursor, and VS Code, enabling create, read, update, move, comment, and search operations on Jira tickets directly from the assistant.

  • Jira JQL Tool

    amiralamox
    F
    license
    -
    quality
    D
    maintenance
    Enables Claude to interact with Jira through JQL (Jira Query Language) queries using the Model Control Protocol, allowing natural language access to Jira issue tracking and project management.

  • jira-gateway

    lfern
    F
    license
    A
    quality
    B
    maintenance
    Exposes Jira task management (list, create with two-step confirmation, start) to AI agents while keeping credentials hidden, and deliberately does not handle git operations.
    3

  • Jira Data Center MCP Server

    ccampora
    F
    license
    A
    quality
    B
    maintenance
    MCP server that connects to Jira Data Center, enabling issue search, retrieval, creation, comments, workflow transitions, project listing, arbitrary JQL, and turning meeting notes into structured Jira stories, tasks, and bugs.
    13