Jira Issue MCP Server

Instructions

Implementation Reference

• src/tools/createIssue.ts:42-109 (handler)

  The main handler function that executes the create_issue tool logic. It validates user authentication via cache, creates a Jira API instance, posts the issue data to Jira's REST API, and returns success/error responses.

  async function handleCreateIssueTool({userEmail, resourceId, summary, description, projectKey, type, priority} : {
      userEmail: string,
      resourceId: string,
      summary: string,
      description: {
          type: "doc"
          version: 1
          content?: any[] | undefined
      },
      projectKey: string,
      type?: 'Task' | 'Bug' | 'Epic' | 'Story',
      priority?: 'Low' | 'Medium' | 'High'}) : Promise<any> {
  
      const cacheData = await getUpdatedCachedData(userEmail);
  
      if(!cacheData) {
          return {
              isError: true,
              content: [
                  {
                      type: "text",
                      text: `Please try again after user confirmed that he authorized the app to access the Jira data.`,
                  },
              ],
          };
      }
  
      const api = getApiInstance(`https://api.atlassian.com/ex/jira/${resourceId}`, cacheData.accessToken);
  
      const response = await api.post(`rest/api/3/issue`, {
          fields: {
              project: {
                  key: projectKey,
              },
              summary,
              description,
              issuetype: {
                  name: type || 'Task'
              },
              priority: {
                  name: priority || 'Medium'
              },
          }
      });
  
      if (response.status !== Constants.CREATED) {
          logger.error('Creating issue failed:', {userEmail, status: response.statusText, data: response.data});
          return {
              isError: true,
              content: [
                  {
                      type: "text",
                      text: `Error creating issue: ${response.statusText}`,
                  },
              ],
          };
      }
  
      logger.info('Issue created successfully:', {summary, description, projectKey, type, priority});
      return {
          content: [
              {
                  type: "text",
                  text: "Issue added successfully!",
              },
          ],
      };
  }

• src/tools/createIssue.ts:9-40 (registration)

  Registration function that defines the 'create_issue' tool with the MCP server. Includes the tool name, description, Zod schema for input validation (userEmail, resourceId, summary, description, projectKey, type, priority), and the async handler wrapper with error handling.

  export function createIssueTool(server: McpServer) {
      server.tool(
          'create_issue',
          'Creates an issue to the users',
          {
              userEmail: z.string().email().describe("The email of the user creating the issue."),
              resourceId: z.string().describe("The ID of the resource being used to call to create the issue."),
              summary: z.string().describe("The title of the issue to be created."),
              description: ADFDocumentSchema.describe("The description of the issue to be created, formatted as an Atlassian Document Format (ADF)."),
              projectKey: z.string().describe("The ID or key of the project where the issue will be created."),
              type: z.enum(['Task', 'Bug', 'Epic', 'Story']).optional().describe("The type of the issue to be created. If not provided, it will default to 'Task'."),
              priority: z.enum(['Low', 'Medium', 'High']).optional().describe("The priority of the issue to be created. If not provided, it will default to 'Medium'."),
          },
          async ({userEmail, resourceId, summary, description, projectKey, type, priority}) => {
              try {
                  return await handleCreateIssueTool({userEmail, resourceId, summary, description, projectKey, type, priority});
              }
              catch(err) {
                  logger.error('Error creating issue:', err);
                  return {
                      isError: true,
                      content: [
                          {
                              type: "text",
                              text: `Error creating issue: ${err instanceof Error ? err.message : 'Unknown error'}`,
                          },
                      ],
                  };
              }
          }
      );
  }

• src/tools/createIssue.ts:13-21 (schema)

  Input schema definition using Zod for the create_issue tool parameters. Validates userEmail (email format), resourceId, summary, description (ADFDocumentSchema), projectKey, and optional type/priority enums.

  {
      userEmail: z.string().email().describe("The email of the user creating the issue."),
      resourceId: z.string().describe("The ID of the resource being used to call to create the issue."),
      summary: z.string().describe("The title of the issue to be created."),
      description: ADFDocumentSchema.describe("The description of the issue to be created, formatted as an Atlassian Document Format (ADF)."),
      projectKey: z.string().describe("The ID or key of the project where the issue will be created."),
      type: z.enum(['Task', 'Bug', 'Epic', 'Story']).optional().describe("The type of the issue to be created. If not provided, it will default to 'Task'."),
      priority: z.enum(['Low', 'Medium', 'High']).optional().describe("The priority of the issue to be created. If not provided, it will default to 'Medium'."),
  },

• src/models/atlassianDocumentSchema.ts:184-188 (schema)

  ADFDocumentSchema definition used for validating the description parameter. Defines the Atlassian Document Format structure with version, type, and content array of block nodes.

  export const ADFDocumentSchema = z.object({
      version: z.literal(1),
      type: z.literal('doc'),
      content: z.array(BlockNodeSchema).optional()
  });

• src/tools/index.ts:6-10 (registration)

  Central registration point where all tools are registered with the MCP server. The createIssueTool is imported and called here as part of the registerTools function.

  export function registerTools(server: McpServer) {
      createIssueTool(server);
      getProjectsTool(server);
      getAccessibleResourcesTool(server);
  }