Skip to main content
Glama
vertigooxyz-devix

Jira MCP Server

by vertigooxyz-devix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JIRA_EMAILYesYour email address associated with the Jira account
JIRA_BASE_URLYesThe base URL of your Jira Cloud instance, e.g. https://your-domain.atlassian.net
JIRA_API_TOKENYesYour Atlassian API token

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jira_list_issue_typesA

List issue types available for a Jira project.

Use this tool to discover which issue types (e.g. Bug, Task, Story) can be used when creating issues in a project. Returns id, name, and description for each type.

Args:

  • project_key (string): Jira project key (e.g. PROJ, DEMO)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON: { "issue_types": [{ "id": string, "name": string, "description": string }] } For Markdown: Formatted list of issue types

Examples:

  • "What issue types can I create in project PROJ?" -> project_key="PROJ"

  • Use before jira_create_issue to get valid issue_type values

Error Handling:

  • 401: Check JIRA_EMAIL and JIRA_API_TOKEN

  • 403: Insufficient permissions for the project

  • 404: Project not found

jira_create_issueA

Create a new Jira issue in a project.

Creates an issue with the given project, summary, and issue type. Use jira_list_issue_types to discover valid issue types for a project.

Args:

  • project_key (string): Jira project key (e.g. PROJ)

  • summary (string): Issue title (required)

  • issue_type (string): Issue type name (e.g. Bug, Task) or numeric ID

  • description (string, optional): Issue description

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON: { "key": string, "id": string, "self": string } For Markdown: Summary with issue key and link

Examples:

  • Create a bug: project_key="PROJ", summary="Login fails", issue_type="Bug"

  • Create a task: project_key="DEMO", summary="Review docs", issue_type="Task"

Error Handling:

  • 401: Check JIRA_EMAIL and JIRA_API_TOKEN

  • 403: No create permission in project

  • 404: Project or issue type not found

  • 422: Validation error (e.g. missing required fields)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are completely distinct: one lists issue types for discovery, the other creates an issue. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tools follow the same 'jira_verb_noun' pattern (jira_list_issue_types, jira_create_issue), making the naming predictable and consistent.

Tool Count3/5

With exactly 2 tools, the server sits in the 'borderline thin' range. While the scope is clear, a Jira server typically needs more tools to be useful.

Completeness2/5

The tools cover only creation and issue-type lookup. Missing get, update, delete, search, and project listing means agents cannot verify or manage issues, leaving significant workflow gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources