Servidor MCP de Summer

• Nombre en el registroai.gosummer/summerverificado en el registro MCP

El nombre en el registro está bajo gosummer.ai. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-27
• Herramientas190
• El servidor se llamasummer
• Versión del servidor0.2.7
• Versión del protocolo2025-06-18

El 2026-10-27 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 288 ms.

• Sus herramientas no hacen ninguno de los casos de uso comprobados: chase pharmacies for delayed orders and notify customers; process approved refunds and confirm settlement in billing tools.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCP55 de 100responde 100 · hace el trabajo 0 · definiciones 86 · contexto 30 · uso 0 · conexión 100
• Qué puede hacer un agente con él0 de 2 casos de uso
• Respondióel 100% de los días7 de 7 comprobaciones diarias
• Mediana de la primera respuesta252 ms
• Espacio en el contexto del agente≈ 75.471 tokenslas definiciones de todas sus herramientas (234), que el agente lleva en cada turno
• Definiciones de herramientasB · 86 de 100
• Resultados tipados0 de 234 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 195 de 234

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• summer_github_issues_read

  Check issue permission and repository visibility, or read one original GitHub issue by number. Restricted to company-selected repositories; no credentials or writes. Issue closure does not resolve the customer case.

• summer_github_connection_read

  Read the company GitHub installation, selected repositories/folders and cached commit status. Makes no GitHub request and returns no credentials.

• summer_github_connection_start

  Get the Summer browser URL for a company administrator to install and authorize the Summer GitHub App. Code access is read-only; issue handoffs use separate GitHub Issues permission and exact case approval. Does not grant access or…

• summer_github_repositories_list

  List repositories available to this company GitHub installation. Provider metadata read; no file content.

• summer_github_folders_list

  Browse repository folders at a branch or commit before selecting access.

• summer_github_sources_save

  Choose repository branches/commits and allowed folders. A dot selects the whole repository. Replaces selections with an expected version and invalidates old cached access. Does not sync code.

• summer_github_sources_sync

  Refresh the selected repository code cache once from GitHub. Reuses the cache for an unchanged commit; sandbox startup never pulls GitHub.

• summer_github_sources_read

  List cached source paths, or read one cached file with path. Only currently selected company folders are available. No live GitHub call or credentials.

• summer_github_connection_disconnect

  Disconnect this company/environment GitHub source access and remove its cached archives.

• summer_reports_themes_get

  Read one saved recurring-issue report and its source snapshot, including reports older than the latest list. Requires current operational company access.

• summer_reports_themes_list

  Read the latest private recurring-issue reports, original case references, source coverage, generation status and human review. Generated themes are suggestions, not verified causes.

• summer_reports_themes_generate

  Generate a private recurring-issue report from the admitted case-summary cohort. One immutable request ID prevents duplicate inference. No customer, knowledge or publication effect.

• summer_reports_themes_review

  Record a human disposition on a saved recurring-issue theme at its expected revision. Retains the original analysis and source references; does not change cases or company knowledge.

• summer_workflows_list

  Read built-in tasks and company/environment-owned workflow templates. Selecting one never runs work.

• summer_workflows_history

  Read the original revisions and authenticated edits for a saved workflow.

• summer_workflows_save

  Save, retire or restore a task template with its expected revision. Changes no case or effect authority.

• summer_workflows_request_text

  Prepare editable operator guidance from an exact active workflow revision and feedback. Starts no investigation and executes no action.

• summer_support_policy_read

  Read business hours, holidays, response commitments and scheduled policy revisions.

• summer_support_policy_update

  Save business hours and response commitments with the expected revision and an effective date.

• summer_saved_replies_list

  Read company saved replies, optionally including retired replies.

• summer_saved_replies_save

  Create, edit, retire or restore a saved reply with its expected revision and reason. Sends nothing. API reference: https://api.gosummer.ai/v1/openapi.json

• summer_saved_replies_history

  Read original revisions of a saved reply.

• summer_saved_views_list

  Read this person's saved inbox views and shared company views.

• summer_saved_views_save

  Save a personal or shared inbox view. Known case filters are normalized by the same service as the UI.

• summer_saved_views_delete

  Remove an owned inbox view, retaining the database's ownership checks.

• summer_quality_scenarios_list

  Read quality scenarios, assessments and current outcomes.

• summer_quality_scenarios_get

  Read one scenario and its saved assessments.

• summer_quality_scenarios_save

  Create, revise or retire a quality scenario, with expected revision and reason.

• summer_quality_assessments_save

  Record an evidence-backed assessment or correction. Does not approve a plan or customer action.

• summer_quality_corrections_list

  Read evidence-backed corrections to previous quality assessments.

• summer_privacy_requests_list

  Read privacy export/deletion requests, status and original event history. Does not export or delete data.

• summer_privacy_requests_create

  File an export or deletion request for human review. Cannot approve, perform or attest completion of the work.

• summer_work_routing_read

  Read eligible teammates and automatic routing for new issues, plan reviews and human tasks.

• summer_work_routing_update

  Save automatic routing for new issues, plan reviews and human tasks with the expected version. Does not grant roles or approval authority.

• summer_router_rules_read

  Read the rules Summer applies before any agent runs, in plain words, with this week's decisions and how often each rule matched. Routing costs no model call.

• summer_router_rules_update

  Save the router rules with the expected version and a reason. Keeps the original revision and updates the Routing rules knowledge document. Run router_rules.test first. Needs a company admin.

• summer_router_rules_test

  Check proposed router rules without saving: lists rule problems, replays recorded ticket activity under the saved and the proposed rules, and routes optional sample facts. Changes nothing.

• summer_router_rules_history

  Read every saved revision of the router rules, with who changed them and why.

• summer_router_rules_decisions

  Read what the router decided and why: totals by outcome, day and rule for the last 7, 30 or 90 days, and pages of decisions with a short plain reason each and the case. Changes nothing.

• summer_cases_engineering_list

  Read private engineering issue associations, optionally checking original GitHub state. Does not close cases or send replies.

• summer_cases_similar_list

  Read bounded original case-summary text matches, with source observation and matching terms. Does not establish customer identity, link cases, call a model or start work.

• summer_slack_discussions_channels

  Read connected Slack posting channels, or inspect the current internal channel name/privacy, posting revision and authenticated sender. Enables no grant and posts nothing.

• summer_cases_discussions_read

  Read original Slack replies for an exact recorded case discussion. A root supplied for an unknown send must match the saved original sender, approved text and operation metadata before its source can be retained. Never posts or approves…

• summer_cases_discussions_list

  Read case-linked Slack discussion receipts and original thread links. Unknown posting stays unknown; no message is sent.

• summer_cases_assignment_read

  Read a case's issue owner, plan reviewer and eligible teammates.

• summer_cases_assignment_update

  Assign an issue owner or plan reviewer with the previous owner as a conflict check. Does not grant roles or approve a plan.

• summer_reports_credits

  Read all-time and month-to-date credits, pending reservations and monthly usage in the company timezone.

• summer_reports_samples_list

  Read paginated original issue/message references behind service counts and timing samples, with date/channel/hour filters in the company timezone. No messages are sent or marked read.

• summer_reports_service_metrics

  Read response and resolution metrics, 90-day daily issue/message and timing trends, and weekday/hour incoming-message heatmaps in the company timezone. Missing timings stay unmeasured.

• summer_reports_agent_timing

  Read how long approved agent runs take: approval to start, each startup and work phase, and each step by action and category, with medians, 90th percentiles and recent runs. Phases that were not recorded stay unmeasured. Starts no work.

• summer_reports_cancellations

  Read cancellation requests and how each ended: paused, renewal moved later, kept, cancelled, or a pause offered with no answer yet. The investigating agent marks each request; the approved plan option sets the outcome. revenue:true adds…

• summer_reports_delivery

  Read delivery attempts, failures and recorded results. Does not retry a delivery.

• summer_delivery_bulk

  Act on several rows from reports.delivery at once: request a new plan, approve each case's current saved plan and run it, or start an approved plan that is waiting. Returns done, skipped or failed with a reason for each row. Rows with no…

• summer_reports_commitments

  Read outstanding customer promises and unfinished work.

• summer_human_tasks_list

  Read work that Summer agents or blocked approvals asked a person to do, with owners, due times, recorded outcomes and change history for one selected task.

• summer_human_tasks_update

  Complete, dismiss, reopen or assign a human task with its expected version. Records the person and outcome. Does not approve a plan or change customer records.

• summer_agent_exclusions_list

  Read the company's sender exclusions and original edit history. Changes retain human approval.

• summer_messenger_conversations_list

  Search and filter the complete Messenger inbox, including visitor conversations without Ops cases.

• summer_messenger_conversations_get

  Read original Messenger messages with saved human sender_display_name, contact form details, read receipts, attachments and timestamped page_context (current page and UI controls) without marking the chat read.

• summer_pharmacy_calls_address_update

  Save a confirmed administrative shipping-address correction for the selected order on a live outbound pharmacy call. Requires an Ops admin and customer-effect access. Does not update carriers or clinical fields; cross-state requests go to…

Las primeras 60 de 190, en el orden del servidor.