Your ambientChat assistant already knows your stuff. Connect an outside service — GitHub, Gmail, Calendar, Slack, Linear, and more — and it can reach their stuff too, right inside the same conversation.
#What It Does
Connected Services lets ambientChat reach out to other tools you use and pull their capabilities into chat. Connect your Gmail and you can ask the assistant to find a reservation email; connect GitHub and it can look up an issue; connect your calendar and it can check next week — all without leaving ambientChat, and all combined with your own inventory, documents, and context.
Under the hood, each connection is an MCP server (the same open standard ambientChat itself speaks), which is why the screen is called MCP servers. Any service that offers an MCP endpoint can be connected by its URL — the service's own docs give it. Services that support it sign you in with OAuth: you approve access on the service's own login screen, and ambientChat never sees your password.
Not to be confused with Context Sharing. Connected Services brings outside tools into ambientChat. The separate Context Sharing setting (see Privacy & Your Data) controls the opposite direction — how much of your ambientChat context is shared out to Claude, brand apps, and partners. Different feature, opposite arrow.
#How to Use It
#iOS App
#Connecting a Service
To connect Gmail, GitHub or another service, add its MCP server — Connected Services live on the MCP servers screen.
- Open the Control tab and tap MCP servers
- Under Add a server, type a Name (e.g. Gmail) and the Server URL
- Choose how it signs in: None, Token (paste the token or API key) or Sign in (OAuth)
- Tap Add server. With Sign in, you're taken to the service's sign-in page — approve the access it asks for
- It's tested as you add it: it appears under Your servers as Connected, with its tool count — or you're told why it can't connect, and nothing is added. An unfinished sign-in shows Needs sign-in
#Using a Connected Service in Chat
Once connected, that service's tools become available to the assistant automatically. Just ask:
- "Any unread email from the landlord?" (Gmail)
- "What's on my calendar Thursday afternoon?" (Calendar)
- "Show me the open issues assigned to me in GitHub."
- "Match my Mercury transactions to the receipts in my library." (a fused answer — your receipts and the connected service together)
You don't call tools by name; the assistant picks the right ones for your question.
#"Do you have my GitHub?" — asking what's connected
The assistant is told, every turn, which services you've connected and roughly what each one can do. So you can just ask — "what services can you reach?" — and get a straight answer rather than a guess.
This also means it shouldn't tell you it can't reach a service you've connected. Earlier versions could: with dozens of tools available, the assistant would sometimes fail to spot the right one and conclude the whole service was missing. It now knows the list up front, and if its first look for a tool comes up empty it tries different wording before drawing any conclusion.
Two things follow from that:
- It won't stall to ask you for something it can look up. Ask about "my app's repo" and it goes and finds it rather than asking you to name it first.
- If it says a service isn't connected, believe it. That answer now comes from the actual list, not from a failed search.
If you have connected a service and the assistant still can't see it, check it is listed under Control → MCP servers. A server whose sign-in was never finished shows Needs sign-in there; tap Sign in to finish it.
#Managing Connections
From MCP servers you can:
- Edit a server's name, URL or token
- Show / hide the token with the eye toggle while you type it. A saved token is never shown again — to change it, type a new one
- Remove a server — its tools leave chat immediately
#Web
The same page is on the web: open Control, go to MCP Servers and click Manage MCP servers. It has the same form: add, test, edit, show/hide token, and remove. Connect on one, and it's available on both.
#Via Chat
You can manage connections conversationally:
- "What services do I have connected?"
- "Connect the MCP server at https://… and call it GitHub — it uses sign-in." The assistant needs the URL. Say whether it uses sign-in or a token; for a sign-in service it hands you the sign-in link
- "Disconnect Slack."
#Via Claude Desktop (MCP)
These tools manage your connections:
list_mcp_servers— List the services you've connected, with status and tool countsadd_mcp_server— Connect a new MCP server by URL (OAuth handled where supported)update_mcp_server— Edit a connection's settings or tokenremove_mcp_server— Disconnect a service
See the MCP Tools reference for details.
#Tips & Tricks
- Connect what you actually use. Each connection adds tools the assistant can reach; a couple of well-chosen services (your email, your calendar) beats a dozen you never query.
- OAuth means no passwords in the app. For supported services you approve access on the provider's own site; ambientChat stores a revocable token, never your password.
- The magic is the mix. The point isn't just reaching Gmail — it's asking one question that combines a connected service and your own inventory and documents (e.g. reconciling bank transactions against your receipts).
- Disconnect cleanly. Removing a service deletes ambientChat's copy of its token and pulls its tools out of chat. If a connection ever looks stale, disconnect and reconnect to refresh it.
#Options
| Setting | What It Does | Default |
|---|---|---|
| Your servers | The outside tools ambientChat can use in chat | None added |
| Token visibility | Show or hide a token while you type it | Hidden |
| Sign-in type | None, Token (Bearer or Raw) or Sign in (OAuth) | None |
#Known Limitations
- The service must speak MCP. You connect a server by its URL, so the service has to offer an MCP endpoint, and you need its address from the service's docs. There is no built-in list of services to pick from.
- Writes ask first. Actions that change something in a connected service (not just read it) go through a confirmation step, and untrusted content coming back from a third-party service is kept away from the assistant's instructions — a deliberate safety boundary. The prompt tells you exactly what will happen (e.g. Linear: Save issue — "Fix beacon drift"), and if you're away from the app an iOS notification with Approve / Deny buttons reaches your lock screen — you have about two minutes before the request expires. If your answer can't be sent from the lock screen (no connection, or the service is having trouble), a second notification, Approval not sent, says "Couldn't send your answer. Open ambientChat to approve or deny." — tap it to open that chat. Whenever you open a chat (or come back to the app, on the phone or the web) while one of its requests is still waiting, the same Approve / Deny prompt appears again, so a request is never lost just because the app was in the background. Tired of approving the same tool? Tap Always allow on the prompt, or manage every tool's policy (Auto / Ask / Blocked) under Control → MCP servers → Tool permissions. Safety-critical actions (emptying trash, deleting your account) always ask.
- A connection is only as available as the service. If the outside provider is down or you revoke access on their side, its tools won't respond until the connection is restored.
#Version History
| Version | Date | What Changed |
|---|---|---|
| 7 | 2026-10-27 | Steps now follow the real screen, Control → MCP servers on the phone and MCP Servers on the web: you add a server by name and URL and choose None, Token or Sign in. There is no list of known services to pick from. Status names, Remove and Tool permissions match the app, and the unsupported "depends on your plan" line is gone AMB-2584 |
| 5 | 2026-10-28 | A lock-screen Approve or Deny that can't be sent now says so with a notification that opens the chat (AMB-2716) |
| 4 | 2026-10-16 | The Settings tab is now called Control, on the phone and the web; the web address is /control (old /settings links still work) (AMB-2120) |
| 3 | 2026-08-07 | The assistant is now told which services you have connected, so it can answer "what can you reach?" accurately, retries a failed tool lookup with different wording instead of concluding a service is missing, and looks things up rather than asking you for details it can find |
| 2 | 2026-07-18 | Approval prompts now name the exact action, arrive as lock-screen Approve/Deny notifications, support "Always Allow", and are manageable per tool under Settings → MCP Servers → Tool Permissions |
| 1 | 2026-07-05 | Initial guide — connect third-party MCP servers (GitHub, Gmail, Calendar, Drive, Slack, Linear, Mercury, or any by URL) with OAuth; use their tools in chat; manage/disconnect (v0.13.2) |