"Fresh" matching MCP servers:

Fetch fresh leads and verify emails in one MCP server

MCP server for Zammad that focuses on workflows the standard Zammad API tooling does not cover well — primarily shared drafts with strict reply-HTML validation, fresh signature rendering and German-localised quote blocks.

Self-hosted Fresha API and MCP server in Python: 17 Fresha tools for appointments, clients, services, team and reviews, on the session of your own Chrome. Personal use.

An MCP server for Freshdesk that identifies which tickets actually need a reply, and provides tools to read, draft, and respond to tickets while respecting your account's custom statuses.

A read-only MCP server that enables AI assistants to query Freshsales CRM data (leads, contacts, deals, accounts) via search, saved views, and record lookup.

Enables fetching and searching Freshdesk tickets, including details like conversations, attachments, and custom fields, via natural language queries.

Enables AI agents to interact with Freshdesk, supporting ticket management, customer and company operations, agent lookup, and knowledge base search through natural language.

Connects Claude to your Freshservice ITSM instance, enabling management of tickets, changes, assets, knowledge base, and more through natural language.

Enables MCP clients to read and write Freshworks CRM data through 30 tools covering leads, contacts, accounts, deals, tasks, appointments and notes, plus unified search and discovery of saved views and field choices. Runs locally over stdio with a personal API key, so records can be looked up, created, updated and annotated in natural language without hosting anything.

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

Enables ticket and contact management via Freshdesk API v2, including listing, searching, and retrieving support tickets and customer contacts.

Enables AI agents to search and read tickets and their conversations, contacts, companies, agents, groups, knowledge base articles, SLA policies, business hours and canned responses, and, on explicit request, create and update records, reply to tickets, add notes, and perform confirmed deletes, merges or conversions. It is stateless and multi-tenant, taking per-request credentials via HTTP headers so every action is performed as the designated agent.

An MCP server that enables AI assistants to interact with Freshservice service desk, supporting ticket search, retrieval, and creation via a configurable, Docker-first deployment.

Connects AI assistants to Freshsales CRM, enabling natural language queries and CRUD operations on contacts, deals, accounts, and more.

Enables agents to read a merchant's helpdesk data—tickets, conversations, contacts, companies, agents, and routing groups—through the Model Context Protocol while handling rate limits and returning partial results when necessary.

Enables AI agents to interact with FreshBooks accounting API for managing clients, invoices, payments, and more through natural language.

Provides 29 tools for Claude to query and update FreshBooks directly, including invoices, clients, estimates, expenses, payments, timesheets, and reports.