On this page
- Understand the two parts of the workflow
- Set up the first connection
- Add a second account deliberately
- Test both accounts with read-only questions
- Keep overlapping tools unambiguous
- Use paired desktop tools when the accounts live there
- Recheck tool selection after an account changes
- Fix account and tool problems
A local phone model can work with more than one connected service without merging all your accounts into one identity. OGAM (Off Grid AI Mobile) Pro supports named MCP server connections, each with its own connection settings and enabled tools.
For multiple accounts, use separate supported connections and check the account behind each result. The provider must support the authentication you need. This is not automatic access to every app installed on the phone.
| Download OGAD | Get OGAM |
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to [email protected], join our Slack community, or talk to us on Reddit.
Understand the two parts of the workflow
The local model runs in OGAM on Android or iPhone. A connected tool runs through an MCP server, which may call an online service. MCP is the connection protocol; it does not make the service offline or remove the provider’s account restrictions.
For example, you might connect a work project service and a personal notes service. You may also create separate manual connections for two accounts at one provider if that provider supports independent authentication sessions.
The important result is account separation you can verify. Two server cards with different names do not prove that their sign-in sessions belong to different accounts.
Set up the first connection
Install OGAM, activate Pro, and choose a local model with tool-calling support. Open Settings → Pro tools and use Add Server.
Choose a supported Quick setup entry, or select Add your own from URL. For a manual connection, use the provider’s actual MCP endpoint, not its ordinary website home page. Give it a clear name such as “Work project account.”
Complete the authentication method required by that server. This can include browser sign-in, a request header, or provider-specific application details. Put credentials in the connection form rather than in a chat prompt.
Wait for the card to show Active. Then open Edit Tools and enable only the tools needed for the first task.
Add a second account deliberately
The quick-setup list marks a preset URL as already added. It is not a universal “add another account” button. If you need another supported connection to that provider, use the manual Add your own from URL form with a distinct name and the provider’s supported authentication setup.
During browser sign-in, check the account chooser. A browser can reuse the account you signed into previously. If both connections return the same identity, correct the authentication before you ask either one to act.
Some providers or server implementations do not support the independent sessions you want. Keep that limit explicit. Separate display names cannot create account isolation that the provider does not offer.
Test both accounts with read-only questions
For the first test, enable a narrow reading tool rather than an editing or sending tool. Ask a question whose answer you can check in the source service.
For example:
Use Work project account to list the current Cedar project items. State which connection was used and show the returned item links. Do not change anything.
Then ask a different known question through the personal connection. Inspect the actual tool result, account context, and links. A model may answer from general knowledge without calling a tool, so a plausible reply alone is not proof that the connection worked.
Keep overlapping tools unambiguous
Two servers can expose tools with similar names. Use Edit Tools on the intended connection and inspect which capabilities are enabled. For the first multi-account checks, temporarily disable overlapping tools on the other connection.
Name the intended connection in the prompt and verify the resulting tool call. Do not rely only on the model’s claim that it selected the right account. If the tool result does not establish the source, narrow the request until you can verify it.
Once the reading flow works, enable additional capabilities only when the task needs them. A service offering editing tools does not mean every search should have those tools active.
Use paired desktop tools when the accounts live there
If you already manage accounts in OGAD (Off Grid AI Desktop), the phone also has a Desktop tools section for paired computers. Enable the intended desktop’s tools through that section and inspect Edit Tools when the connection is ready.
This is a separate route from signing into a standalone MCP server directly on the phone. The desktop must be reachable and able to execute its tools. Do not assume that pairing alone copied every account credential to the phone.
Use the displayed execution device and source account in your checks. A request started from the phone can still depend on the desktop and its online account connections.
Recheck tool selection after an account changes
In mobile beta 114, a tool stays tied to the source account or server you selected. Changing that source can turn the affected tool off until you choose the intended source again. This prevents a tool with the same name at another connection from silently taking its place.
After changing an account, open its tool settings and inspect the on/off state. Select the intended source, enable only the tools you want, and run a small read-only check with a known result. Ask for the source account in that check and inspect the actual tool result.
If a server has no available tools, read its displayed connection state and tool count separately. A saved server entry does not prove that a usable tool was returned. Resolve the provider or connection problem before enabling another similarly named tool as a substitute.
Fix account and tool problems
| Symptom | Next check |
|---|---|
| Both connections show the same data | Provider sign-in identity and reused browser session |
| A card is Active but no call occurs | Enabled tools and local model tool support |
| Wrong account answers | Named connection, overlapping tools, and actual call result |
| A desktop tool is unavailable | Pairing, tool grant, and desktop reachability |
| Sign-in needs extra details | Provider’s supported application configuration |
Disconnect or remove connections you no longer use. For account-backed services, review the provider’s own access settings when you want to revoke authorization there as well.
Open Pro tools in OGAM and verify one read from each intended account. Once those source identities are clear, use the same named connections for the next task without mixing their results.