Freshdesk と統合する MCP サーバーの実装により、AI モデルは Freshdesk モジュールとやり取りし、さまざまなサポート操作を実行できます。

##特徴

• Freshdeskインテグレーション:Freshdesk APIエンドポイントとのシームレスなインタラクション -AIモデルサポート: Freshdesk でサポート業務を遂行するAIモデルを有効に
• 自動チケット管理: チケット作成、更新、応答の処理

コンポーネント

ツール

サーバは、Freshdesk 操作のための複数のツールを提供しています。

• 入力:

• subject: チケット料金

• description: チケット説明

• [source] (必須) チケットソースコード

• [priority] (必須) チケット優先レベル

• [status] (必須) チケットステータスコード

• [email] (文字列、オプション): リクエスト者のメール

• [requester_id (番号、オプション): リクエスト者の ID

• [custom_fields] (オプション) チケットで設定するカスタムフィールド

• [additional_fields] (オプション) 追加のトップレベルフィールド

• [update_ticket: 既存のチケットの更新

• 入力:

Freshdesk MCP Server

An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support operations.

Features

• Freshdesk Integration: Seamless interaction with Freshdesk API endpoints
• AI Model Support: Enables AI models to perform support operations through Freshdesk
• Automated Ticket Management: Handle ticket creation, updates, and responses

Components

Tools

The server offers several tools for Freshdesk operations:

• create_ticket: Create new support tickets

  • Inputs:
    • subject (string, required): Ticket subject
    • description (string, required): Ticket description
    • source (number, required): Ticket source code
    • priority (number, required): Ticket priority level
    • status (number, required): Ticket status code
    • email (string, optional): Email of the requester
    • requester_id (number, optional): ID of the requester
    • custom_fields (object, optional): Custom fields to set on the ticket
    • additional_fields (object, optional): Additional top-level fields

• update_ticket: Update existing tickets

  • Inputs:
    • ticket_id (number, required): ID of the ticket to update
    • ticket_fields (object, required): Fields to update

• delete_ticket: Delete a ticket

  • Inputs:
    • ticket_id (number, required): ID of the ticket to delete

• search_tickets: Search for tickets based on criteria

  • Inputs:
    • query (string, required): Search query string

• get_ticket_fields: Get all ticket fields

  • Inputs:
    • None

• get_tickets: Get all tickets

  • Inputs:
    • page (number, optional): Page number to fetch
    • per_page (number, optional): Number of tickets per page

• get_ticket: Get a single ticket

  • Inputs:
    • ticket_id (number, required): ID of the ticket to get

• get_ticket_conversation: Get conversation for a ticket

  • Inputs:
    • ticket_id (number, required): ID of the ticket

• create_ticket_reply: Reply to a ticket

  • Inputs:
    • ticket_id (number, required): ID of the ticket
    • body (string, required): Content of the reply
    • cc_emails (array of strings, optional): Additional email addresses added to the ‘cc’ field of the outgoing email. These supplement the ticket requester, who always remains the primary recipient
    • bcc_emails (array of strings, optional): Additional email addresses added to the ‘bcc’ field of the outgoing email. These supplement the ticket requester, who always remains the primary recipient
    • from_email (string, optional): Email address the reply is sent from