Your assistant works with
the tools you already use.
Your assistant is only as helpful as the tools it can reach. Connect the apps you already use, and it gets to work where the work happens — with access only to what you allow, and a readable log of everything it does.
How connections work
Connecting a tool gives your assistant a specific job to do, not the keys to everything. You decide what it can reach, and every action it takes is logged.
Connect once
Sign in once to give your assistant access to a tool — only as much as the job needs. No shared logins, no copy-pasted keys.
Only what you allow
Every connection starts read-only until you allow more. Your assistant never sees anything you didn't hand it.
A readable log of everything
Every action your assistant takes is recorded — what it did, when, and what it touched — so you can always look back. (Full technical detail, including scope and payload, is there for those who want it.)
Turn it off anytime
Disconnect a tool and your assistant loses that access the instant you click — nothing lingers.
Connect almost anything else.
Don't see your tool above? You're not stuck. If it has a modern connection (an MCP server) or an API, your assistant can use it — and we can help hook up almost anything else, so it shows up alongside everything else.
- Connect any MCP server, public or private, with its URL.
- Turn an internal API (REST or GraphQL) into a tool in minutes.
- Set up a connection once and reuse it across all your assistants.
{
"transport": "mcp",
"server": "https://mcp.acme.dev",
"scopes": ["read:tickets", "write:notes"],
"auth": "oauth"
}apps connected and counting · new ones added every week
Give your assistant just the access it needs —
and nothing it doesn't.
Set up in about a minute, connect the tools you already use, and watch the work start moving on its own.