Saltar al contenido
Logo de Replo Support Agent

Servidor MCP de Replo Support Agent

Qué servidores MCP son de Replo Support Agent, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-11-10

← Volver a Replo Support Agent

De quién es el servidor
  • Nombre en el registroio.github.replohq/replopublicado por replohq en GitHub

Publicado por la organización replohq en GitHub, la misma que enlaza la portada de replo.app. El registro vincula ese espacio de nombres a un inicio de sesión en GitHub.

Cuando le preguntamoscomprobado el 2026-11-21
  • Estadorespondecomprobado el 2026-11-21
  • Herramientas135
  • El servidor se llamareplo
  • Versión del servidor1.0.0
  • Versión del protocolo2025-06-18

El 2026-11-21 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 158 ms.

¿Debe un agente conectarlo?

Aún no está claro
  • El 19 nov 2026 llamamos a sus herramientas de lectura con un escenario fijo, y solo 0 de 1 pasos devolvieron lo que la comprobación espera.

Una vez conectado

  • create_site, update_site, publish_site, update_site_navigation, update_site_metadata cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Sus definiciones ocupan unos 58932 tokens de contexto: activa solo las herramientas que necesita la tarea.
  • Parámetros sin tipo o sin descripción en 66 de 135 herramientas: revisa los argumentos antes de llamar.

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.

Medido cada día

comprobaciones diarias: 16, la primera el 2026-11-07
  • Nota INITE MCP62 de 100responde 100 · definiciones 92 · contexto 30 · conexión 100 · rebajada hasta que una de nuestras ejecuciones de escenario se supere · rebajada por las señales de aviso de abajo
  • Comprobado con una llamada0 de 1 pasos superadosúltima ejecución 19 nov 2026, solo llamadas de lectura
  • Respondióel 100% de los días16 de 16 comprobaciones diarias
  • Mediana de la primera respuesta206 ms
  • Espacio en el contexto del agente≈ 58.932 tokenslas definiciones de todas sus herramientas (135), que el agente lleva en cada turno
  • Definiciones de herramientasA · 92 de 100
  • Resultados tipados0 de 135 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 66 de 135

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_site, update_site, publish_site, update_site_navigation, update_site_metadata

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 →

Herramientas que ofrece135 herramientas · leído el 2026-11-22
  • get_agent_sessiondescrita por el servidor

    Retrieve a Replo session's current status, latest response, tool activity, errors, and pending interactions (permission requests and questions). Use to check progress after starting or continuing a session. When pendingInteractions is…

  • resolve_agent_interactioncambia datosdescrita por el servidor

    Resolve one pending Replo agent interaction with the user's explicit answer. For a permission request, pass type permission and the decision from its response options. For a question, pass type question and one answers array per form…

  • abort_agent_sessioncambia datosdescrita por el servidor

    Cancel the in-progress turn of a Replo session. Cancellation interrupts unfinished work and may leave partial changes. Completed changes are not rolled back, and the session is retained. For multi-step Replo work, read the replo skill…

  • query_replo_analyticsdescrita por el servidor

    Run read-only ClickHouse SQL over a project's Replo analytics for traffic, conversion, revenue, and session-level questions. No saved Insights report is required. Use this for ad hoc questions or when list_insights_reports finds no…

  • list_sitesvista, aún sin llamar

    Find the Replo site to inspect, manage, or clone within a project. Each site returns clone_url, the URL used to clone that site's code over Git, and is_default. When the user does not name a site, use the site with is_default true; if no…

  • create_sitecambia datosdescrita por el servidor

    Create a site in a Replo project together with its git repository, forked from a published starter template ('blank' unless template is given). Pass projectId from list_projects and a name for the site. Returns the site with clone_url…

  • update_sitecambia datosdescrita por el servidor

    Rename a Replo site's dashboard display name. This does not change its SEO page title, which lives in the site's layout metadata, or its published page content. Use list_sites to find site IDs. For multi-step Replo work, read the replo…

  • publish_sitecambia datosdescrita por el servidor

    Publish a site to make changes live. Requires the siteId from list_sites. Builds, packages, uploads, and deploys. Before publishing, read the publishing-sites skill (call skills with name "publishing-sites").

  • apply_branding_to_sitecambia datosdescrita por el servidor

    Apply the project's saved brand to the selected site's shared style tokens, fonts, layout, and shared components. Affects that site's drafts, not the saved brand kit. Use update_brand first if there is no saved brand. Starts an…

  • update_site_navigationcambia datosdescrita por el servidor

    Update the selected site's shared navigation, header, or footer in its layout and shared components. Shared component changes affect all pages using them. Starts an asynchronous internal-agent operation; poll get_agent_session. For…

  • update_site_metadatacambia datosdescrita por el servidor

    Update site-wide SEO title, description, social preview, favicon references, or search visibility in the selected site's root layout. Does not rename the dashboard label. Starts an asynchronous internal-agent operation; poll…

  • update_site_trackingcambia datosdescrita por el servidor

    Add, change, or remove a user-requested analytics or marketing script in the selected site's root layout. Name the provider, identifiers, and requested behavior. After publication, the script may send visitor data to that provider. Starts…

  • list_tasksvista, aún sin llamar

    List a project's Replo automations (scheduled tasks). For multi-step Replo work, read the replo skill (call skills with name "replo").

  • get_taskdescrita por el servidor

    Inspect the schedule and current timing of a specific Replo automation (scheduled task). For multi-step Replo work, read the replo skill (call skills with name "replo").

  • create_taskcambia datos

    Schedule a Replo automation: a prompt Replo's agent runs later for the project, once or on a recurrence (rrule). It does not run now. Each run happens without the user, so the prompt must be self-contained, and you should confirm the…

  • update_taskcambia datos

    Change a Replo automation (scheduled task). Read it with get_task first: title, prompt and rrule are always replaced, so pass the current values for any the user isn't changing, and pass the current emoji too or it resets to ✨; omitting…

  • delete_taskcambia datosdescrita por el servidor

    Permanently delete a Replo automation (scheduled task) and stop all future runs. Use this when the user no longer wants a scheduled prompt to run. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • get_integration_statusdescrita por el servidor

    Check one integration's connection status in the selected Replo project. Returns connected, not_connected, or needs_reconnect. needs_reconnect means every connection is stale; a connection's own needsReconnect flag marks a stale one when…

  • get_brandingdescrita por el servidor

    Read the live brand: version, facts, the business and design overviews (markdown), colors with roles (hex is authoritative), fonts, marks, personas, tagged context files, the Brand Studio imagery (the merchant's own photos, the first…

  • update_brandcambia datosdescrita por el servidor

    Create or update the saved brand kit, with `ops` or from a public site's `url`. Never applies branding to an existing site or publishes it. `ops`: business facts, the business and design overviews, colors, fonts, personas, logo marks, and…

  • create_artifactcambia datosdescrita por el servidor

    Save a new HTML artifact in Files from files you wrote, in about a second. Send files keyed by path: index.html is the page, each *.insights.json is an Insights report, and report.insights.json is the main report (Replo renders the page…

  • update_artifactcambia datosdescrita por el servidor

    Replace parts of an existing artifact with content you wrote, keeping its folder ID, link and sharing. If the artifact is shared by link, the change is visible to anyone with that link, including people outside the workspace…

  • generate_artifactcambia datosdescrita por el servidor

    Have Replo's agent research, write and save an artifact from a request in words, including Insights reports, using existing reports, analytics, or files as sources. Pass fileId (the artifact folder ID) to revise an existing artifact in…

  • show_artifactdescrita por el servidor

    Show a saved artifact to the user as an inline card they can expand and scroll, in hosts that draw cards. Call it once after create_artifact or update_artifact saves one, after generate_artifact's session reports the saved artifact, or…

  • get_artifact_view_accessdescrita por el servidor

    Used by the artifact card to load the artifact it shows. Not for direct use: call show_artifact to show an artifact.

  • get_artifact_report_contextdescrita por el servidor

    Used by the artifact card to draw a live Insights report it shows. Not for direct use: call get_insights_report to read a report.

  • run_artifact_chartdescrita por el servidor

    Used by the artifact card to load the live numbers for a chart or report it shows. Not for direct use: call query_insights_report to query a report.

  • create_shared_previewcambia datosdescrita por el servidor

    Create or recover a public live preview link to a site page without publishing. Anyone with the URL can view the draft from your account's existing preview workspace. Use projectId from list_projects and siteId from list_sites; supply the…

  • revoke_shared_previewcambia datosdescrita por el servidor

    Disable a public shared preview link using the id returned by create_shared_preview. Only its creator with current project access or a workspace admin can revoke it. Repeating the request succeeds; page content is preserved. Revoke only…

  • find_ordersdescrita por el servidor

    Find storefront orders when investigating a payment state or fulfillment state. Returns order summaries only: no customer contact details or payment identifiers are included. To look up a known customer's orders, pass their address as the…

  • get_orderdescrita por el servidor

    Inspect the public record of one storefront order: line items, fulfillment, refunds, and event history. The customer's contact address is masked (`j••••@example.com`) and no payment identifiers are returned. Money amounts are integers in…

  • replo_forms_listdescrita por el servidor

    List a project's forms with their questions and settings: contact forms, quote requests, signups and booking forms. Use a form's id with replo_form_responses_list to read what people sent, or with replo_form_summary_get for totals per…

  • replo_forms_getdescrita por el servidor

    Get one form: its questions in order, status, close date, response limit, thank-you message and where responses are forwarded. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_forms_createcambia datosdescrita por el servidor

    Create a form on a project. Sites that render forms from their live definition show it at once; otherwise add it to the site code by its key. To forward responses, set destinations.webhookUrl, then call replo_forms_webhook_secret_rotate…

  • replo_forms_updatecambia datosdescrita por el servidor

    Change a form's name, status, questions, notifications, forwarding, close date, response limit, thank-you message or quiz scoring. Only the fields you pass change; fields replaces the whole question list. Set status to archived to stop…

  • replo_forms_webhook_secret_rotatecambia datosdescrita por el servidor

    Make a new signing secret for a form's webhook and return it. This is the only time it's shown, and the old secret stops working at once. Each delivery carries a Replo-Signature header, t=<unix seconds>,v1=<hex>: recompute HMAC-SHA256…

  • replo_form_summary_getdescrita por el servidor

    Totals per question across one form's latest 10,000 responses (all of them for most forms; summarizedResponses says how many were counted): counts per choice, the average and range of numbers and ratings, the date range of dates, and the…

  • replo_form_responses_listdescrita por el servidor

    List what people sent through a project's forms, newest first: answers keyed by question key, the contact, the page and campaign tags. Filter to one form with formId and to recent responses with since, then follow next_cursor for older…

  • replo_form_responses_getdescrita por el servidor

    Get one response to a form: every answer keyed by question key, the contact, the page it was sent from and its campaign tags. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_form_contacts_listdescrita por el servidor

    List the people who answered a project's forms or booked, newest first, with their email, name and phone. Follow next_cursor for older pages; use replo_form_contacts_get for one person's responses and bookings. For multi-step Replo work…

  • replo_form_contacts_getdescrita por el servidor

    Get one person who answered a form or booked, with their responses (newest first) and bookings. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_event_types_listdescrita por el servidor

    List the event types visitors can book on a project, such as a 45-minute haircut, with their length, booking rules, add-ons and staff. Use an event type's id with replo_booking_slots_list to find open times. For multi-step Replo work…

  • replo_event_types_getdescrita por el servidor

    Get one event type with its length, booking rules (buffer, notice, booking window, slot spacing, reminder), add-ons and staff. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_event_types_createcambia datosdescrita por el servidor

    Create an event type visitors can book, such as a 45-minute haircut. It has no staff yet: add people or tables with replo_booking_staff_add before anyone can book it. Unset rules get the defaults: 30-minute slot spacing, 1 person at a…

  • replo_event_types_updatecambia datosdescrita por el servidor

    Change an event type's name, description, location, length, booking rules, add-ons or Google Meet setting. Only the fields you pass change; addOns replaces the whole list. Existing bookings keep their times. For multi-step Replo work…

  • replo_booking_staff_addcambia datosdescrita por el servidor

    Add a teammate, or a table, bay or room, to an event type so visitors can book them. Pass the opening hours (scheduleId) they work for it. A teammate is named by their email and must already be on the project; adding someone who is…

  • replo_booking_staff_updatecambia datosdescrita por el servidor

    Change a staff member's share of bookings (weight) or the opening hours they work for one event type. With no staff member chosen, a booking goes to whoever is free with the fewest upcoming bookings for their weight, so weight 2 gets…

  • replo_booking_staff_removecambia datosdescrita por el servidor

    Take a staff member off one event type so visitors can no longer book them for it. Their existing bookings stay. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_booking_schedules_listdescrita por el servidor

    List a project's opening-hours schedules: weekly hours in a time zone, plus closed dates and one-off hours. Staff work a schedule per event type. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_booking_schedules_getdescrita por el servidor

    Get one opening-hours schedule: its time zone, weekly hours, closed dates and one-off hours. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_booking_schedules_createcambia datosdescrita por el servidor

    Create opening hours: weekly hours in a time zone, with up to six time ranges a day for split shifts, plus closed dates and one-off hours. Give a staff member their own schedule with replo_booking_staff_add or replo_booking_staff_update…

  • replo_booking_schedules_updatecambia datosdescrita por el servidor

    Change a schedule's name, time zone, weekly hours or date overrides. Only the fields you pass change; weeklyHours and overrides each replace the whole list. Add a closed day as an override with no ranges. Existing bookings keep their…

  • replo_booking_slots_listdescrita por el servidor

    List the times an event type can be booked between from and to (at most 62 days), as visitors see them: inside opening hours and booking rules, minus existing bookings and busy times on linked Google Calendars. Each slot names a staff…

  • replo_bookings_listdescrita por el servidor

    List a project's bookings that start between from and to (at most 92 days), earliest start first, with the person each is for. Includes cancelled and no-show bookings, so filter on status when counting visits. Follow next_cursor for the…

  • replo_bookings_getdescrita por el servidor

    Get one booking: its event type, staff member, time, status, party size, add-ons, Meet link and the person it's for. For multi-step Replo work, read the replo skill (call skills with name "replo").

  • replo_bookings_createcambia datosdescrita por el servidor

    Book an event type for someone, as the business does for a phone or walk-in booking in the Forms app. The time may fall outside opening hours, but not on top of another booking. The person is saved as a contact and the booking goes on the…

  • replo_bookings_cancelcambia datosdescrita por el servidor

    Cancel a confirmed booking, as the business does in the Forms app: Replo emails the person that it's cancelled, alerts the team, removes it from linked calendars and tells anyone waiting for that day that a time opened up. A past or…

  • replo_bookings_reschedulecambia datosdescrita por el servidor

    Move a confirmed booking to a new start time with the same staff member, as the business does in the Forms app: Replo emails the person the new time, resets the reminder and moves the calendar event. The new time may fall outside opening…

  • replo_bookings_updatecambia datosdescrita por el servidor

    Record how a confirmed booking went: completed when the visit happened, no_show when the person didn't come. Cancels its pending reminder. To cancel or move a booking, use replo_bookings_cancel or replo_bookings_reschedule. For multi-step…

  • find_assetsdescrita por el servidor

    Find media and files in a project's asset library using semantic search or library metadata. For multi-step Replo work, read the replo skill (call skills with name "replo").

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

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "replo": {
      "type": "http",
      "url": "https://api.replo.app/v1/mcp"
    }
  }
}

Añadirlo

Claude Code, en una terminal

claude mcp add --transport http replo https://api.replo.app/v1/mcp

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://api.replo.app/v1/mcp como conector personalizado en los ajustes.

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.