PipedreamHQ/pipedream

**Feature Request: Additional Freshdesk MCP Tools**

Open

#20630 opened on Apr 17, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)JavaScript (7,438 stars) (5,305 forks)batch import
actionenhancementgood first issueprioritizedtriaged

Description

Hi Pipedream team,

We're using the Freshdesk MCP connector to power a Claude AI agent for our Ad Operations team. The agent is designed to retrieve ticket details, search past tickets for resolution guidance, and surface knowledge base articles — but we're currently blocked by a few missing tools in the connector.

We'd like to request the following Freshdesk API endpoints be added:

Ticket Retrieval

  • GET /api/v2/tickets/{id} — Retrieve a single ticket by ID including description and custom fields
  • GET /api/v2/tickets/{id}/activities — Retrieve ticket activity/audit log (status changes, reopens, assignments)

Ticket Search & Filtering

  • GET /api/v2/search/tickets?query="{field}:{value}" — Search tickets using Freshdesk's filter query syntax
  • GET /api/v2/tickets?status={n}&per_page=30 — List tickets filtered by status with pagination

Currently available tools cover ticket management actions (set status, priority, assign, add notes, list conversations) which are great, but without the ability to retrieve or search tickets by ID or filter, it's difficult to build read-based workflows on top of the connector.

Use case context: We're building a Claude-powered resolution agent that takes a ticket number, pulls the full ticket body and conversation thread, extracts keywords, searches our Freshdesk Solution Articles knowledge base, and returns recommended next steps. Steps 1 and 2 of that workflow are currently blocked without GET /tickets/{id} and the activities endpoint.

Happy to provide more context or test any additions. Thanks for the great work on the MCP connectors!

— Paul from Aragon Ad Operations

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
apitoolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Freshdesk REST API v2Understanding of Pipedream's connector architectureBasic knowledge of MCP (Model Context Protocol)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the existing Freshdesk MCP tools in the Pipedream repository (likely under components/freshdesk). Understand the pattern for adding new tools, including how endpoints are defined and how authentication is handled. The issue lists specific endpoints: GET /tickets/{id}, /tickets/{id}/activities, /search/tickets, and /tickets with filtering. Implement each endpoint following the existing patterns, ensuring proper error handling and pagination. Check if the assignee has any associated branches or comments for guidance.