OpenAlly.ai Agent for Android MCP server

Which MCP servers are OpenAlly.ai Agent for Android's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to OpenAlly.ai Agent for Android

Whose server it is

Addresshttps://mcp.openally.ai/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on openally.ai when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-27

Stateanswerschecked 2026-10-27
Tools25
Server calls itselfOpenAlly
Server version1.0.1
Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 165 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 6 of the 7 days it takes to judge reliability.

Once connected

Keep approval on for send_link_to_device: they delete, send or pay without saying so.
send_link_to_device, create_note, update_note, delete_note, create_support_ticket change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-27

INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
Answeredmeasuring6 of the 7 daily checks it takes to print a share
Median first answer231 ms
Space in an agent's context≈ 4,053 tokensthe definitions of all its tools (25), which an agent carries on every turn
Tool definitionsA · 100 of 100
Typed results25 of 25 toolsdeclared outputSchema: results come typed, read once

Every tool passes all six checks.

What an agent can do with it

not sure · Build automated workflows to manage inventory, orders, and payments
cannot · Create social media content drafts with images and videos
not sure · Set up app automations to handle routine business tasks

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

Tools that delete, send or pay, marked as not destructive: send_link_to_device
Tools that change data, on a server that answers without a sign-in: send_link_to_device, create_note, update_note, delete_note, create_support_ticket

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers25 tools · read 2026-10-27

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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "openally": {
      "type": "http",
      "url": "https://mcp.openally.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http openally https://mcp.openally.ai/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.openally.ai/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.