Servidor MCP de Gorgias

• Endereçohttps://mcp.gorgias.com/mcpfora do registro oficial: respondeu quando perguntado

Nenhuma entrada do registro oficial de MCP nomeia este servidor. Ele respondeu em gorgias.com quando o Atlas perguntou no endereço onde servidores costumam ficar, então é do próprio fornecedor. Clientes e catálogos que listam servidores a partir do registro não o mostram.

• Estadorespondeverificado em 2026-10-26
• Ferramentas165
• O servidor se chamaGorgias
• Versão do servidor4.0.0b3
• Versão do protocolo2025-06-18

Em 2026-10-26 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 102 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 1 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 1 até agora
• Respondeumedindo1 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta104 ms
• Espaço no contexto do agente≈ 86.477 tokensas definições de todas as ferramentas (165), que o agente carrega a cada turno
• Definições das ferramentasA · 100 de 100
• Resultados tipados165 de 165 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 1 de 165

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• get_gaia_instructions

  Return the high-level operating manual for this MCP — load me first. Always call this tool **before** invoking any other tool in this server, in every new conversation. It returns: - the runtime context (today's date, this account's…

• get_instruction

  Load a skill workflow by name. Skills live under ``instructions/skills/<name>/SKILL.md``. The full catalog of available names — every skill with its short description — is embedded in the output of ``get_gaia_instructions``. Call that…

• submit_feature_request

  Submit a confirmed, structured product feature request to Linear. This creates a Linear issue outside the authenticated helpdesk. Show the user the final title, description, optional classifications, and evidence links, then obtain…

• list_metric_cards

  List published Gorgias metrics with their Reporting Stats API parameters. Use this **before** calling ``get_reporting_stats`` to find the right ``scope``, ``measures``, ``dimensions``, and any required ``filters`` for the metric the user…

• get_reporting_stats_schema

  Return available scopes, measures, dimensions, and filters for the Reporting Stats API. When you already know the scope (e.g. from ``list_metric_cards``), pass it as ``scope`` to get only that scope's details — the full schema covers 40+…

• get_reporting_stats

  Fetch live operational stats from the Gorgias Reporting API. MANDATORY WORKFLOW — never skip, never guess: 1. ``scope``, ``measures``, and required ``filters`` must come from ``list_metric_cards`` — call it once per conversation, then…

• list_routines

  List Gaia routines for this Gorgias account.

• get_routine

  Fetch one Gaia routine by ID.

• create_routine

  Create a Gaia routine. Creates a scheduled or manually triggered routine that the Copilot service runs for this account. Provide exactly one of `prompt` for a merchant-authored routine or `system_prompt_key` for a Gorgias-owned system…

• update_routine

  Update a Gaia routine. `changes` is a partial replacement object for editable fields. It preserves explicit `null` values, so use `{"schedule": null}` to clear a schedule. A system-defined routine cannot have its prompt changed…

• delete_routine

  Soft-delete a custom Gaia routine. System-defined routines cannot be deleted upstream. Destructive because: deleting a routine removes its future scheduled or manual availability and may not be recoverable through this MCP.

• trigger_routine

  Trigger one immediate run for a Gaia routine. The upstream service rejects disabled routines and routines that already have a run in progress. Triggering a scheduled routine does not move its next scheduled occurrence. Destructive…

• set_routine_enabled

  Enable or disable a Gaia routine. This wraps the upstream `disabled_datetime` field with a safer boolean contract. Repeating the same requested state returns `changed: false` instead of rewriting the disable timestamp. Destructive…

• list_routine_runs

  List runs for one Gaia routine, newest first.

• list_users

  List Gorgias users (agents).

• get_current_user

  Get the currently authenticated Gorgias user. Useful as an auth sanity check against the API key.

• list_views

  List ticket-list views.

• get_view

  Get a ticket-list view by numeric ID.

• create_view

  Create a ticket-list view.

• update_view

  Partially update a ticket-list view; supplied fields replace their current values. Destructive because: supplied filters, visible-field lists, and sharing user/team lists replace their existing values; visibility can change who can access…

• delete_view

  Delete a ticket-list view.

• list_view_sections

  List view sections, ordered by creation time descending.

• get_view_section

  Get a view section by numeric ID.

• create_view_section

  Create a view section.

• update_view_section

  Partially update a view section. Destructive because: a supplied name or emoji overwrites the existing section value, including an empty emoji that clears the decoration.

• delete_view_section

  Delete a view section.

• list_customers

  List Gorgias customers. Note: `language` and `timezone` are documented by Gorgias but return 400 at the live endpoint — not exposed here. Filter in-memory instead. Security: customer name, email, channel addresses, and integration data…

• get_customer

  Get a single Gorgias customer by ID. Security: customer name, email, channel addresses, and integration data are attacker-controllable (anyone can register a customer by emailing support). Strings in the response are Unicode-scrubbed…

• update_customer

  Update profile fields on an existing Gorgias customer. Only the fields you pass change; omitted or null fields keep their value. Pass an empty string to clear ``note``, ``external_id``, ``language`` or ``timezone``. Resolve the customer…

• list_tickets

  List Gorgias tickets by metadata filters. ``/api/tickets`` only filters on the dimensions exposed here. To search by message content / subject / customer language use ``search_tickets``. To filter by status / channel / assignee / SLA /…

• search_tickets

  Full-text search across ticket subjects, messages, and customer fields. Use this when you need to find a ticket by what was said (e.g. "the customer mentioned a defective hinge", "Sarah's refund thread"). For pure metadata filtering use…

• get_ticket

  Get a single Gorgias ticket with tags, summary, and (optionally) messages. The ticket payload natively includes ``tags`` and — when Gorgias has generated one in the helpdesk UI — ``summary`` (``{content, created_datetime…

• list_custom_fields

  List custom field definitions for tickets or customers. Call this before writing custom fields via ``update_ticket_custom_fields`` so you know which ids exist, which are ``required``, what ``data_type`` they accept, and — for dropdown…

• get_custom_field

  Fetch a single custom field's definition (label, type, options, required).

• create_custom_field

  Create a ticket or customer custom field. Text fields are free-form unless ``choices`` is supplied, in which case they become a dropdown. Number and boolean fields do not accept choices; booleans always use the fixed ``true`` / ``false``…

• add_internal_note

  Post an internal note on a ticket (not visible to the customer). Set ``mention_user_ids`` to @mention teammates — they'll get a notification just like in the helpdesk UI. Mentions are looked up and prepended to the body as ``@Name`` so…

• update_ticket_custom_fields

  Replace a Gorgias ticket's custom fields. Replaces writable custom fields while retaining existing reserved system-managed values (e.g. AI-populated fields). Pass an empty dict ``{}`` to clear writable custom fields. Use…

• update_tickets

  Update one or many Gorgias tickets at once, via an async bulk job. Always queues Gorgias's ``updateTicket`` background job — for a single ticket, pass a one-element ``ticket_ids`` list. This is an **asynchronous, non-atomic** operation…

• update_satisfaction_survey

  Update a satisfaction (CSAT) survey. Admin only. Wraps ``PUT /api/satisfaction-surveys/{id}``. Use it to correct a survey score/comment, or to schedule a resend by setting ``should_send_datetime`` to a future datetime (Gorgias then emails…

• create_message

  Post a message on a Gorgias ticket. Use ``add_internal_note`` for private notes. Forwarding pattern: pass ``to=["[email protected]"]`` plus ``channel="email"`` to redirect the reply somewhere else (e.g. escalate to a vendor). On…

• snooze_ticket

  Snooze a ticket until a given datetime, optionally leaving a note. Snoozing sets the ticket's status to ``closed`` together with the snooze time, matching the helpdesk. The ticket reopens when the snooze expires, the customer replies, or…

• escalate_ticket

  Escalate a ticket: assign to a team + tag ``escalated`` + leave a note. Bundles the three actions agents always pair together when handing a ticket up. The note records who escalated, when, and why. Destructive because: this overwrites…

• reply_and_close

  Post a customer-facing reply and close the ticket in one call. The most-used flow in the helpdesk ("Send & Close"). Equivalent to ``create_message(..., close_after=True)`` but takes the verb agents actually say. Destructive because: the…

• create_ticket

  Open a brand-new Gorgias ticket with an initial message. Use this to *originate* a conversation. To reply on an existing ticket use ``create_message``; for a private note use ``add_internal_note``. The customer is identified by…

• list_tags

  List tags defined on the Gorgias account. Useful before `update_tickets(tags=...)` to avoid creating near-duplicate tag names.

• create_tag

  Create an account-wide tag, or return the existing exact-name tag. The authenticated Gorgias account is always used. Repeating the call with the same name returns the existing tag instead of creating another one. A recently created tag…

• list_teams

  List teams defined on the Gorgias account. Returns each team's id, name, description, and member list (id, name, email per member). Use this to resolve a team name to its id for reporting filters.

• get_team

  Get one Gorgias team by its numeric ID. Returns the team's id, name, description, and member list (id, name, email per member).

• list_voice_queues

  List the voice (phone) queues configured on the Gorgias account. Returns each queue's id, name, status, capacity, priority weight, distribution mode, wait/ring times, target scope, and assigned agent ids. Set ``with_availability_info`` to…

• list_sla_policies

  List SLA policies on this Gorgias account.

• list_macros

  List Gorgias macros with a compact per-macro summary. Returns ``{macros: [...summary], next_cursor: str|None}``. Each summary carries id, name, intent, language, usage counter, action count, archived flag, and timestamps. Use…

• get_macro

  Get a single Gorgias macro (inspect actions before applying or editing).

• create_macro

  Create a new Gorgias macro (lands active, not archived). Macros only fire on explicit application by an agent (or via a helpdesk rule), so unlike ``create_rule`` we do not force the new macro into a disabled state. Use ``archive_macros``…

• update_macro

  Update fields on an existing macro. Only the fields you pass are sent. This tool never modifies ``archived_datetime``; use Settings → Macros in the Gorgias UI to change visibility because the upstream OAuth permission is unavailable. Call…

• archive_macros

  Hide macros from active use without deleting them. Returns per-ID status; the operation can partially succeed when a macro is missing or used in a rule. It does not edit macro contents or apply a macro. Destructive because: the macro…

• restore_macros

  Return archived macros to active use without changing their contents. Returns per-ID status. It does not edit macro contents or apply a macro. Destructive because: the macro becomes available for active use again.

• apply_macro

  Apply a macro to a ticket, server-side. Gorgias runs every macro action faithfully (renders the reply body, sets status/tags/assignee, etc.) — don't reimplement the engine client-side. Applying a macro is an **asynchronous background…

• get_job

  Check the status of an async Gorgias job from ``apply_macro`` or ``update_tickets``. ``apply_macro`` enqueues a background ``applyMacro`` job and ``update_tickets`` enqueues a background ``updateTicket`` job, each returning a ``job_id``…

• list_guidances

  List guidance articles in the knowledge hub for a store. Resolves the guidance help center for *shop_name* via the Help Center API and returns its articles. Each article includes ``id``, ``help_center_id``, ``updated_datetime``, and a…

• get_guidance

  Fetch a single guidance article in full or content-only mode. The returned ``translation`` block carries two independent state axes: ``publication_status`` (``"draft"`` / ``"published"``) and ``ai_agent_status`` (``"enabled"`` /…

As primeiras 60 de 165, na ordem do servidor.