Saltar al contenido
Logo de Mako Metrics

Servidor MCP de Mako Metrics

Qué servidores del registro oficial de MCP son de Mako Metrics, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-19

← Volver a Mako Metrics

De quién es el servidor
  • Nombre en el registrocom.makometrics/mako-metricsverificado en el registro MCP

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

Cuando le preguntamoscomprobado el 2026-10-19
  • Estadorespondecomprobado el 2026-10-19
  • Herramientas16
  • El servidor se llamamako-metrics
  • Versión del servidor1.1.0
  • Versión del protocolo2025-06-18

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

Medido cada díacomprobaciones diarias: 2, la primera el 2026-10-19
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta243 ms
  • Espacio en el contexto del agente≈ 3388 tokenslas definiciones de todas sus herramientas (16), que el agente lleva en cada turno
  • Definiciones de herramientasA · 94 de 100
  • Parámetros sin descripción: en 6 de 16

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_order, create_client, set_brand_profile

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. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece16 herramientas · leído el 2026-10-19
  • list_plans

    List Mako Metrics plans with pricing, what's included, scope limits, delivery, guarantee, and links to verify the merchant. Use this to recommend a plan before ordering. Covers the competitor report plans, which are the only products…

  • create_order

    Create a Mako Metrics order brief for a customer and return a Stripe checkout link for them to complete payment. After payment, we email the customer when the report is ready, typically within 24h. They download the PDF report and export…

  • whoami

    Show which Mako Metrics account this key belongs to: the plan, how many competitor reports are left in the current period, and the client workspaces on the login. Call this first in any session that will use the customer tools. Requires…

  • list_clients

    List the client workspaces on this account, with the id each other tool needs and whether the client's brand profile is ready for a May run. Requires an X-Mako-Key header.

  • order_report

    Order a competitor Meta ads report for one competitor. On a Dominator, Agency or May plan this spends one report from the current period's allowance and queues the build. On Snapshot it returns a Stripe checkout link instead. The report…

  • run_may

    Start a May creative run for one client: research, copy, and eight ad concepts, delivered to the portal for the customer to review and edit. Usually a few minutes. When the brand profile names a competitor May has not researched yet, it…

  • get_status

    Check one report order or one May run by its id, or omit the id to list the most recent of both. Returns the status and, once finished, the deliverable id to pass to get_download_url. Requires an X-Mako-Key header.

  • list_deliverables

    List everything finished and ready to download on this account: competitor report bundles and May run artifacts. Requires an X-Mako-Key header.

  • get_download_url

    Mint a download link for one deliverable. The link works for 10 minutes and then expires, so fetch it when the human is ready to use it rather than in advance. Requires an X-Mako-Key header.

  • create_client

    Add a client workspace to the account. Each workspace holds one brand's profile, runs, creatives and campaigns. Plans include a fixed number of active clients, so this fails when the roster is full. Needs the May plan and an X-Mako-Key…

  • draft_brand_from_website

    Read a client's website and fill in most of their brand profile automatically. Takes up to a minute or two. The result is a DRAFT: review it with get_brand_profile, correct it with set_brand_profile, then confirm. This is the fastest way…

  • get_brand_profile

    Read one client's brand profile: what they sell, who buys it, voice, colors, and the campaign defaults. Also reports whether it is confirmed and, if not, exactly which answers are still missing before May can run. Requires an X-Mako-Key…

  • set_brand_profile

    Write or update one client's brand profile. Every field is optional and only what you pass is changed, so this is safe to call repeatedly to correct a website draft. Pass confirm: true when the answers are right, which is what run_may…

  • list_creatives

    List the ad concepts from a May run: headline, primary text, call to action, compliance status, and a download link for each image. Returns the newest version of each concept. Use the variant_id values with build_paused_campaign. Requires…

  • list_meta_assets

    Show the client's connected Facebook ad account and the conversions available to optimize toward. Call this before build_paused_campaign on a leads or sales campaign, because those need a conversion to aim at. Connecting Facebook itself…

  • build_paused_campaign

    Build a real Meta campaign from chosen concepts, in the client's own ad account, left PAUSED. It cannot deliver and cannot spend until a person turns it on in Ads Manager, which this tool cannot do and neither can any other. Takes a…

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": {
    "mako-metrics": {
      "type": "http",
      "url": "https://ufupdlaxddckqxbgbhwu.supabase.co/functions/v1/mcp"
    }
  }
}

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.