Skip to main content
Glama

Codex Jira Stories MCP

Local MCP server that lets the Codex CLI query Jira Cloud and publish already-reviewed stories. It was designed to work with the local jira-stories skill: the skill writes the story; this server queries the project and creates or updates the issue.

Flow security

  • Credentials are not stored in the repository: they are read from JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN.

  • Write tools require confirmPublish: true.

  • There is no deletion tool.

  • Before publishing, use jira_preview_issue and check the result.

Related MCP server: jira-mcp-server

Preparation

  1. Copy .env.example to a safe location and export the variables in the terminal. Do not create or version a .env file with credentials.

  2. Confirm that the account has Browse projects and Create issues permissions on the desired Jira project.

  3. Register the server in the Codex CLI:

codex mcp add jira-stories \
  --env JIRA_BASE_URL="$JIRA_BASE_URL" \
  --env JIRA_EMAIL="$JIRA_EMAIL" \
  --env JIRA_API_TOKEN="$JIRA_API_TOKEN" \
  -- node /Users/emenezes/projetos/codex-jira-stories-mcp/src/server.mjs

Then open a new Codex session and run /mcp to confirm that jira-stories is active.

Available tools

Tool

Usage

jira_list_projects

Lists projects visible to the account.

jira_get_issue_types

Lists issue types for a project.

jira_get_create_fields

Shows the required and editable fields for creating the issue.

jira_search_issues

Searches for issues by JQL.

jira_preview_issue

Builds the preview without accessing or changing Jira.

jira_create_issue

Creates an issue, only with confirmPublish: true.

jira_update_issue

Updates the allowed fields of an issue, only with confirmPublish: true.

Conversation example

Write a functional story to allow PDF report export. Query the available Jira projects, generate a preview for the AGR project, and only publish after I approve.

To publish an approved preview, explicitly ask Codex to use jira_create_issue with confirmPublish: true. The description is converted from plain text or basic Markdown to the document format accepted by Jira Cloud.

Local verification

npm test

Current limitations

This first version supports Jira Cloud via API token. For environments with mandatory SSO or a delegated authorization requirement, the next step is to replace the authentication with OAuth 2.0 on the MCP server, preserving the same tools.

Available Tools

7 tools
jira_create_issueB

Cria uma issue no Jira. Exige confirmPublish: true após revisão.

Inputs: summary (required), projectKey (required), description (required), issueTypeId (required), +4 more.

jira_get_create_fieldsA
Read-only

Lista os campos disponíveis e obrigatórios ao criar uma issue para projeto e tipo.

Inputs: projectKey (required), issueTypeId (required).

jira_get_issue_typesA
Read-only

Lista os tipos de issue permitidos no projeto informado.

Inputs: projectKey (required).

jira_list_projectsA
Read-only

Lista os projetos Jira que a conta pode visualizar.

Inputs: no named parameters.

jira_preview_issueA
Read-only

Gera os campos que seriam publicados, sem chamar o Jira.

Inputs: summary (required), projectKey (required), description (required), issueTypeId (required), +3 more.

jira_search_issuesA
Read-only

Busca issues existentes por JQL para evitar duplicidade.

Inputs: jql (required), maxResults.

jira_update_issueC

Atualiza campos de uma issue existente. Exige confirmPublish: true.

Inputs: fields (required), issueKey (required), confirmPublish (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: list projects, get metadata, search issues, preview, create, and update. The main potential confusion is between jira_get_create_fields and jira_preview_issue, since both relate to issue creation fields, though one describes the schema and the other previews actual values.

    Naming Consistency5/5

    Every tool follows the same jira_<verb>_<noun> pattern using snake_case. The verbs are clear and consistently used, making the tool set highly predictable.

    Tool Count5/5

    Seven tools is well-scoped for a Jira issue creation/update workflow. Each tool serves a necessary step in the process without unnecessary redundancy.

    Completeness4/5

    The workflow covers project discovery, issue type/field metadata, duplicate checking, preview, creation, and update. A direct get-single-issue tool is missing but search can serve that purpose, and deeper Jira lifecycle operations like transitions are outside the apparent scope.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Jira issues via JQL search, epic management, comments, attachments, and issue CRUD, with support for both Cloud and Server/Data Center instances.
      9
      11 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Code CLI to interact with Jira, including fetching issue details, searching issues with JQL, retrieving comments, and getting user info, with support for multiple Jira environments.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.
      22
      1,575 npm
      Apache 2.0