Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

create_ticket

Create support tickets in Zendesk with subject, description, priority, status, assignee, and tags to track customer issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesTicket subject
commentYesTicket comment/description
priorityNoTicket priority
statusNoTicket status
requester_idNoUser ID of the requester
assignee_idNoUser ID of the assignee
group_idNoGroup ID for the ticket
typeNoTicket type
tagsNoTags for the ticket

Implementation Reference

  • The handler function that executes the core logic of the create_ticket tool. It constructs the ticket data from inputs and calls zendeskClient.createTicket, handling success and error responses.
    handler: async ({
      subject,
      comment,
      priority,
      status,
      requester_id,
      assignee_id,
      group_id,
      type,
      tags,
    }) => {
      try {
        const ticketData = {
          subject,
          comment: { body: comment },
          priority,
          status,
          requester_id,
          assignee_id,
          group_id,
          type,
          tags,
        };
    
        const result = await zendeskClient.createTicket(ticketData);
        return {
          content: [
            {
              type: "text",
              text: `Ticket created successfully!\n\n${JSON.stringify(
                result,
                null,
                2
              )}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            { type: "text", text: `Error creating ticket: ${error.message}` },
          ],
          isError: true,
        };
      }
    },
  • Input schema using Zod for validating parameters of the create_ticket tool, defining required and optional fields like subject, comment, priority, etc.
    schema: {
      subject: z.string().describe("Ticket subject"),
      comment: z.string().describe("Ticket comment/description"),
      priority: z
        .enum(["urgent", "high", "normal", "low"])
        .optional()
        .describe("Ticket priority"),
      status: z
        .enum(["new", "open", "pending", "hold", "solved", "closed"])
        .optional()
        .describe("Ticket status"),
      requester_id: z.number().optional().describe("User ID of the requester"),
      assignee_id: z.number().optional().describe("User ID of the assignee"),
      group_id: z.number().optional().describe("Group ID for the ticket"),
      type: z
        .enum(["problem", "incident", "question", "task"])
        .optional()
        .describe("Ticket type"),
      tags: z.array(z.string()).optional().describe("Tags for the ticket"),
    },
  • src/server.js:47-52 (registration)
    The registration loop that registers all tools, including 'create_ticket' from ticketsTools, by calling server.tool() for each tool object.
    // Register each tool with the server
    allTools.forEach((tool) => {
      server.tool(tool.name, tool.schema, tool.handler, {
        description: tool.description,
      });
    });
  • Supporting helper method in ZendeskClient class that makes the actual Zendesk API POST request to create a ticket.
    async createTicket(data) {
      return this.request("POST", "/tickets.json", { ticket: data });
  • src/server.js:32-32 (registration)
    Inclusion of ticketsTools (containing create_ticket) into the allTools array for subsequent registration.
    ...ticketsTools,

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JurreBrandsenInfoSupport/zendesk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server