Model Context Protocol (MCP) server for Gorgias customer support platform - extract customer email data for automation projects
12 tools with complete schemas and descriptions, but quality is uneven. Most tools have adequate naming (verb_noun pattern) and descriptions (100-250 chars), meeting baseline expectations. However, parameter descriptions lack depth, many omit format constraints, ranges, or usage context. Output schemas are not documented. Error handling is generic. No tool annotations (readOnlyHint/destructiveHint). Composition is sound: tools are single-responsibility and chainable. Security: API credentials injected server-side (good). Overall: solid foundation, but falls short of production-grade polish expected for A-tier tools.
Create new customers for automation workflows. Enables programmatic customer creation with channels and metadata.
Extract customer email data in a structured format suitable for spreadsheet automation. Aggregates customer information with ticket statistics.
Get detailed customer information including channels and integrations. Provides comprehensive customer data for automation workflows.
Get list of integrations configured in Gorgias account. Retrieve integration settings and status for automation setup.
Get detailed information about a specific ticket including customer data, messages, and metadata.
List customers for contact management and email extraction. Supports filtering by email and external ID.
Output schemas not documented. Tools return data but LLMs cannot plan downstream calls without knowing response structure. E.g., gorgias_list_tickets returns tickets but response fields are undocumented.
Parameter descriptions lack format constraints and usage context. E.g., 'cursor' params have no explanation of format or how to obtain initial cursor. 'date_from'/'date_to' state ISO 8601 format but lack examples of valid ranges.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe reads from destructive writes without explicit hints. gorgias_send_reply and gorgias_update_ticket are destructive but unmarked.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
List events from Gorgias for monitoring and automation. Retrieve system events, user actions, and ticket changes.
Get all messages for a specific ticket, including customer and agent communications.
List Gorgias tickets with filtering options for customer email extraction. Supports pagination and various filters to find specific tickets.
Search tickets using Gorgias search syntax. Powerful tool for finding specific tickets based on multiple criteria.
Send replies to tickets (outgoing messages, internal notes, or simulated incoming messages). Enables automated customer responses and internal communication.
Update ticket properties including status, assignee, tags, and priority. Essential for automated ticket management workflows.
Error handling is generic. transformError() maps errors to MCP codes but does not guide recovery. E.g., 'Rate limit exceeded' does not suggest retry delay or alternative actions.
gorgias_send_reply has complex conditional parameters (sender_email required for outgoing/internal, receiver_email required for outgoing only). Dependencies not documented; LLMs will guess wrong parameter combinations.