MCP Connectors: Your Phone as the Client
Point the app at a Model Context Protocol server and its tools appear beside the built-in ones — your home automation, your notes service, your own scripts.
Point MyBenAI at a Model Context Protocol server and the tools that server offers appear beside the built-in ones, callable by the assistant on your phone.
What that gets you
MCP is how an assistant is given access to a system without that system having to know anything about the assistant. Your home automation, your notes service, an internal service at work, your own scripts on a machine at home — if it speaks MCP, your phone can be the client.
The direction is worth noticing. Most AI integrations mean handing your data to a vendor's model. Here the model is on your phone and reaches out to the things you point it at, so the data flows toward you rather than away.
Adding one
Settings → Connectors. Give it the endpoint and its credentials; the app reads the server's tool manifest and adds what it advertises. Presets are included for common cases. Each connector can be switched off without deleting it, and its tools obey persona allowlists like any other.
These are network tools
A connector talks to something that is not your phone, so every call is written to the network log with its destination, and offline mode switches connectors off along with everything else that needs the network. Both facts are visible to you, which is the point of recording them.
If it does not speak MCP
Use a REST connector and describe the HTTP API directly.
Looking for something else? Every page on this site.