Saltar al contenido
Logo de SAGOT

Servidor MCP de SAGOT

Qué servidores MCP son de SAGOT, 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-10-28

← Volver a SAGOT

De quién es el servidor
  • Nombre en el registrocom.sagots/sagotverificado en el registro MCP

El nombre en el registro está bajo sagots.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-28
  • Estadorespondecomprobado el 2026-10-28
  • Herramientas136
  • El servidor se llamasagot
  • Versión del servidor0.1.0
  • Versión del protocolo2025-06-18

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

¿Debe un agente conectarlo?No conectarlo
  • Sus herramientas no hacen ninguno de los casos de uso comprobados: check shipment status and supplier timelines by phone; compare supplier answers against criteria and flag gaps.
  • Comprobado 5 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • waitlist_update, waitlist_delete, invitations_create, account_delete, workspaces_create cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Sus definiciones ocupan unos 26328 tokens de contexto: activa solo las herramientas que necesita la tarea.
  • Parámetros sin tipo o sin descripción en 123 de 136 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íacomprobaciones diarias: 5, la primera el 2026-10-28
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 5 hasta ahora
  • Qué puede hacer un agente con él0 de 2 casos de uso
  • Respondiómidiendo5 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta599 ms
  • Espacio en el contexto del agente≈ 26.328 tokenslas definiciones de todas sus herramientas (136), que el agente lleva en cada turno
  • Definiciones de herramientasC · 68 de 100
  • Resultados tipados0 de 136 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 123 de 136
  • Sin indicar si solo lee o puede destruir: 136 de 136

Qué puede hacer un agente con él

  • no está claro · book a restaurant table by phone when no online booking exists
  • no puede · check shipment status and supplier timelines by phone
  • no puede · compare supplier answers against criteria and flag gaps

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: waitlist_update, waitlist_delete, invitations_create, account_delete, workspaces_create

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 ofrece136 herramientas · leído el 2026-10-28
  • access_info

    Read public registration availability (closed alpha is the default) and whether the caller's session or credential is valid (signedIn).

  • waitlist_join

    Request alpha participation with contact consent. Does not create an account or send email.

  • waitlist_list

    Platform operators only: review the alpha queue, oldest first, with status and pagination.

  • waitlist_update

    Platform operators only: mark an applicant waiting, contacted or closed.

  • waitlist_delete

    Platform operators only: permanently remove an applicant's waitlist information. Does not delete their account or invitations.

  • invitations_create

    Platform operators only: issue an email-bound, single-use private invitation. Returns the token once; share privately. Does not send email. Replaces prior unused invitations for that email.

  • invitations_list

    Platform operators only: list invitation states without tokens, newest first.

  • invitations_revoke

    Platform operators only: revoke an unused invitation. Existing accounts are unaffected.

  • account_register

    SAGOT account.register. Uses the same authorization and validation as website, API and CLI.

  • account_login

    SAGOT account.login. Uses the same authorization and validation as website, API and CLI.

  • account_me

    SAGOT account.me. Uses the same authorization and validation as website, API and CLI.

  • account_logout

    SAGOT account.logout. Uses the same authorization and validation as website, API and CLI.

  • account_acceptTerms

    Signed-in session only: accept the current Terms of Service, Data Processing Addendum and Privacy Notice (version from account.me termsVersion). Records the version and time on your account.

  • account_mfaSetup

    Signed-in session only: start turning on two-step sign-in. Confirms your password and returns a new authenticator secret and otpauth:// URI (scan as a QR code). Nothing changes until account.mfaEnable confirms a code.

  • account_mfaEnable

    Signed-in session only: confirm a 6-digit code from the authenticator app to turn two-step sign-in on. Returns 10 one-time recovery codes once; store them safely. Sign-in then needs a code (account.login code).

  • account_mfaDisable

    Signed-in session only: turn two-step sign-in off with your password and a current code or recovery code. SAGOT staff cannot use the platform console without it.

  • account_mfaRecoveryCodes

    Signed-in session only: replace all recovery codes after confirming a current code. Returns the 10 new codes once.

  • account_delete

    Signed-in session only: delete your own SAGOT account after confirming your password. Refused while you own a workspace (transfer ownership or delete it first) or hold a SAGOT staff role. Removes you from every workspace, revokes your…

  • assistants_preview

    Check an OAuth authorization request from an AI assistant (Claude, ChatGPT, Gemini or any MCP client) before consent: returns the assistant's name, the address it returns to, the scopes requested in plain words, or the problem with the…

  • assistants_authorize

    Signed-in session only: allow (with a workspaceId) or deny an AI assistant's request to use SAGOT. Allowing gives that assistant the listed scopes in one workspace — never admin, never more than your role — and returns redirectTo, the…

  • assistants_list

    Signed-in session only: AI assistants connected to your account through OAuth, with workspace, scopes, when connected and last used.

  • assistants_revoke

    Signed-in session only: disconnect an AI assistant. Its access and refresh tokens stop working immediately; it must ask again to reconnect.

  • assistants_clients_create

    Signed-in session only: create an OAuth client ID and secret for an assistant that asks for them, such as Gemini Enterprise (redirect https://vertexaisearch.cloud.google.com/oauth-redirect). The secret is returned once. People who sign in…

  • assistants_clients_list

    Signed-in session only: OAuth client IDs you created for assistants, with their redirect addresses.

  • assistants_clients_revoke

    Signed-in session only: revoke an OAuth client ID you created; assistants using it can no longer sign in or refresh tokens.

  • workspaces_create

    SAGOT workspaces.create. Uses the same authorization and validation as website, API and CLI.

  • workspaces_list

    SAGOT workspaces.list. Uses the same authorization and validation as website, API and CLI.

  • workspaces_update

    SAGOT workspaces.update. Uses the same authorization and validation as website, API and CLI.

  • workspaces_region

    Owner only, signed-in session: choose where AI providers process this workspace's call audio and text — "eu" (European Union) or "us" (United States). No call starts until a region is chosen. Choosing it means accepting this statement: "I…

  • workspaces_delete

    Owner only, signed-in session: permanently delete this workspace and everything in it — agents, contacts, calls, recordings, transcripts, lines, API keys and members' access. confirmName must equal the workspace name. Refused while calls…

  • members_list

    List the people in this workspace with their roles (viewer, editor, operator, admin, owner). Admins also see invitations and their status; tokens are never shown.

  • members_invite

    Admins: invite an email to this workspace with a role, optionally limited to agentIds (viewer/editor/operator only). SAGOT emails the invitation when email is configured; the one-time link path (/join#member=…) is also returned once as a…

  • members_update

    Admins: change a member's role and, with agentIds, limit a viewer/editor/operator to selected agents (null = all agents). Takes effect on their next request, including their API keys. The owner's role cannot change; only the owner grants…

  • members_transfer

    Owner only, signed-in session: make another member the owner. You become an admin; any agent limit on them is removed. The new owner is emailed.

  • members_remove

    Admins remove a member; any member may remove themselves to leave. The owner cannot be removed. Their sessions and API keys stop working in this workspace immediately.

  • members_revoke

    Admins: revoke a pending member invitation by id so its link stops working.

  • members_preview

    Public: show what a member invitation link grants (workspace, inviter, role, invited email, status) before accepting.

  • members_accept

    Signed-in account session only: accept a member invitation issued to this account's email and join the workspace with its role.

  • credentials_create

    SAGOT credentials.create. Uses the same authorization and validation as website, API and CLI.

  • credentials_list

    SAGOT credentials.list. Uses the same authorization and validation as website, API and CLI.

  • credentials_revoke

    SAGOT credentials.revoke. Uses the same authorization and validation as website, API and CLI.

  • agents_create

    SAGOT agents.create. Uses the same authorization and validation as website, API and CLI.

  • agents_list

    SAGOT agents.list. Uses the same authorization and validation as website, API and CLI.

  • agents_get

    SAGOT agents.get. Uses the same authorization and validation as website, API and CLI.

  • agents_save

    SAGOT agents.save. Uses the same authorization and validation as website, API and CLI.

  • agents_test

    Validate the current draft and its integration. This is configuration validation, not a voice-quality score. Use a draft SIP call to hear the result.

  • agents_publish

    Publish a validated draft for new calls. Active calls keep their original snapshot.

  • agents_pause

    SAGOT agents.pause. Uses the same authorization and validation as website, API and CLI.

  • agents_rollback

    Point new calls to a previous published version.

  • agents_retire

    SAGOT agents.retire. Uses the same authorization and validation as website, API and CLI.

  • integrations_save

    SAGOT integrations.save. Uses the same authorization and validation as website, API and CLI.

  • integrations_list

    SAGOT integrations.list. Uses the same authorization and validation as website, API and CLI.

  • integrations_get

    SAGOT integrations.get. Uses the same authorization and validation as website, API and CLI.

  • integrations_test

    Exercise the connector with a test payload. Sandbox never writes to an external product.

  • integrations_disconnect

    SAGOT integrations.disconnect. Uses the same authorization and validation as website, API and CLI.

  • contacts_import

    SAGOT contacts.import. Uses the same authorization and validation as website, API and CLI.

  • contacts_list

    SAGOT contacts.list. Uses the same authorization and validation as website, API and CLI.

  • contacts_history

    Review all retained calls, conversations, outcomes, actions, follow-ups and activity for one contact across agents in this workspace. Missing or deleted evidence is labeled.

  • contacts_export

    Export the contact's retained evidence as a readable Markdown or structured JSON audit snapshot. Export is logged; it does not create recordings or recover deleted content.

  • contacts_update

    SAGOT contacts.update. Uses the same authorization and validation as website, API and CLI.

Las primeras 60 de 136, 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": {
    "sagot": {
      "type": "http",
      "url": "https://sagots.com/mcp"
    }
  }
}

Añadirlo

Claude Code, en una terminal

claude mcp add --transport http sagots https://sagots.com/mcp

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://sagots.com/mcp como conector personalizado en los ajustes.

Especificación OpenAPI

136 rutas, leído el 2026-10-28. Abrir la especificación ↗

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.