Your app, inside the AI assistants people already use

People now ask ChatGPT, Claude and Gemini to get things done, not just to answer questions. Your app can be part of that. With a connection in place, a customer, or your own team, can look something up or take an action in your app from the assistant they already have open, without opening the app.

What it looks like

Someone asks their assistant, "What's on my plate this week?" The assistant asks your app, and answers from the real data: a review on Tuesday, a payment due Thursday, a call on Friday. Then they say, "Move Thursday's to Monday," and it's moved, in your app, the same as if they'd tapped through it themselves.

Three things make that work:

• Ask. People get answers from your app's real data, in plain language.
• Act. They ask for a change, and it happens in your app.
• Stay in control. You choose what an assistant can see and what it can do. It sits behind the same sign-in as the app, so people only ever reach their own data.

How it's built

The connection is an MCP server. MCP (the Model Context Protocol) is the open standard these assistants use to connect to apps and services. We build a small server that describes what your app can do (look up the week, move an item, add a note), and the assistant calls it when it's useful. Nothing about your app changes for the people who never use an assistant.

It can be for your customers, or just for your team. A lot of the time the second one comes first: an owner who can ask "how many sign-ups this week?" or "reply to that review" without logging in to anything.

When it makes sense

It's not for every app. It earns its place when people come back to your app to check something or to do something small and frequent, and when an assistant is already where they spend their day. We look at that in Evaluate & Explore. If it's worth doing, it's scoped there: as part of a build, or added to an app you already have.

Ask about connecting your app