Servidor MCP de OpenAlly.ai Agent for Android

• Direcciónhttps://mcp.openally.ai/mcpno está en el registro oficial: respondió al preguntarle

Ninguna entrada del registro oficial de MCP nombra este servidor. Respondió en openally.ai cuando el Atlas preguntó en la dirección donde suelen montarse los servidores, así que es del propio proveedor. Los clientes y catálogos que listan servidores a partir del registro no lo muestran.

• Estadorespondecomprobado el 2026-10-27
• Herramientas25
• El servidor se llamaOpenAlly
• Versión del servidor1.0.1
• 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 165 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 6 de los 7 días necesarios para juzgar su fiabilidad.

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 MCPtras una semanala nota necesita 7 comprobaciones diarias: 6 hasta ahora
• Respondiómidiendo6 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta231 ms
• Espacio en el contexto del agente≈ 4053 tokenslas definiciones de todas sus herramientas (25), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados25 de 25 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

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 →

• explain_connecting

  How a person connects their OpenAlly account, for when a tool has answered that no account is connected or the person asks how to connect. Returns fixed text and nothing else: it connects nothing, signs nobody in, reads no account and…

• explain_openally

  A short, accurate description of OpenAlly for a given topic: overview, providers, privacy, platforms, business or apps. Static text from the app's own guide; needs no account.

• search_openally_docs

  Search the OpenAlly app guide for a question about the app: where a screen is, how to set something up, what a feature does. Returns up to five short excerpts with the guide slug to fetch next.

• get_app_guide

  Fetch one section of the OpenAlly app guide by slug: app-guide, app-map, app-recipes, app-destinations, app-providers, app-skills-tools, app-aster, app-privacy-support. Start with app-guide, then the slug it points at.

• get_account_summary

  A one-glance summary of the connected OpenAlly account: when it was created, whether setup is complete, whether it has a plan, and how many devices are signed in when this connection may also see devices. No email, no ids.

• get_setup_status

  Whether the connected OpenAlly account has finished onboarding and has a model selected, and which provider and model its last synced settings name. This does not test the model or its credentials. Use it before walking someone through…

• get_plan_status

  The plan state of the connected OpenAlly account, in facts only: whether a plan is active, when the current period ends, what it includes in plain words, and credits left. Only for questions about existing plan status. Do not call this…

• list_connected_assistants

  Every assistant currently connected to the OpenAlly account, with what each may access and when it was connected and last used. Disconnecting is done in the OpenAlly app under Profile, Security.

• list_devices

  The devices signed in to the connected OpenAlly account: platform, app version, label, when each was last seen and whether it can receive notifications. Call it before any device tool; the device_ref values it returns are what those tools…

• notify_device

  Send a short notification to the devices signed in to the connected OpenAlly account, or to one device by device_ref. The person sees it as a normal notification from OpenAlly.

• open_app_screen

  Send a notification that opens one screen of the OpenAlly app when tapped. screen_id must be an id from the app-destinations guide, exactly as written; some screens are Android-only and are refused for an account with no Android device…

• send_link_to_device

  Send an https link to the devices signed in to the connected OpenAlly account, or to one device by device_ref, as a notification that opens the link when tapped. The link's host is shown in the notification. For a screen inside the…

• ask_device_agent

  Send a prompt to the agent running in the OpenAlly app on the person's device. The action runs on the signed-in device under the access granted at connection time; the outcome is recorded and the person receives a notification. OpenAlly…

• get_action_result

  Read the current state of a device action started by ask_device_agent or get_business_snapshot, by its action_id. Starts nothing new.

• get_business_snapshot

  Today's counts from OpenAlly Business on the person's device: orders and bookings today, open orders, low-stock items. Counts only, nothing about customers, no money. OpenAlly must be available on the phone. The read runs under the…

• create_note

  Create a note in the person's OpenAlly notes. It is stored in their account and appears in Notes on every signed-in device the next time it syncs, marked as added by this assistant.

• list_notes

  The person's OpenAlly notes, most recently updated first, with a short preview of each. Use search_notes to find one by content.

• search_notes

  Search the person's OpenAlly notes by words in the title, body or tags. Returns up to 10 with a preview and the note_ref to use with update_note or delete_note.

• update_note

  Replace the title, body, tags or pinned state of one of the person's OpenAlly notes. Only the fields given change; a field edited on a device at the same time keeps the later edit. Find the note_ref with search_notes first.

• delete_note

  Delete one of the person's OpenAlly notes. It disappears from every device on the next sync. Ask before deleting; find the note_ref with search_notes first.

• create_support_ticket

  Open a support ticket with the OpenAlly team as the person. Use it when the guide does not answer the question or something is broken. The reply arrives in the OpenAlly app under Support and can be read here with get_support_ticket.

• get_support_ticket

  The person's support tickets with their status and who wrote last, or one ticket by ticket_ref. Message bodies stay in the app.

• reply_support_ticket

  Add the person's reply to one of their support tickets. With no ticket_ref, the most recently updated open ticket is used.

• close_support_ticket

  Close one of the person's support tickets. Replying later reopens it. Ask before closing.

• create_feature_request

  File a feature request with the OpenAlly team as the person.