GitHub for code, MCP servers for everything else. You decide which tools of each connection an agent may call, and in which Space. Autopilot is an MCP server too, for Claude, ChatGPT and other MCP clients.
Your chat can reach into Autopilot. Your agents can reach out to a service. They are set up separately, and neither one opens the other.
Claude or ChatGPT signs in as you. It gets what you allowed at sign-in and never more than your own permissions. More on bringing your AI.
Each tool of a connected server is granted to a Role on its own. An agent without the grant is refused.
An agent receives the result of a call. It never receives the token that made it.
Morrow connects its store so Sales Analyst can report on orders. Nobody wants an agent editing products on day one.
Paste the MCP server's address and sign in over OAuth. Keep the connection for the whole company or for one Space.
Autopilot lists the tools the server reports, each marked as a read or a write.
Start with the read-only set, or pick tools by name. Sales Analyst gets the order list and nothing that changes the store.
If the server changes what a tool accepts, that tool stops working until someone reviews it again.
Install the app on the repositories you choose. Agents push to the Task's branch, the pull request appears on the Task as a Change Request, and publishing takes someone who holds the publish permission. See Projects.
Any remote MCP server with OAuth sign-in. An Automation can read yesterday's orders and post the digest every morning.
Create Tasks, search the Library and check on Runs from the chat. Your published Skills show up in the client as prompts.
GitHub is built in. Everything else connects through an MCP server, the vendor's or your own, and you grant its tools one by one.
No. Connecting Claude to Autopilot lets Claude use Autopilot. Connecting a store to Autopilot lets agents use the store. Each is its own setup with its own grants.
No. Only tools you reviewed and granted to one of the agent's Roles can be called. See Roles and approvals for how permissions work.
The connection's sign-in is stored encrypted on the Autopilot server and used there when a call is made. For GitHub, Autopilot issues a short-lived token for each piece of work.
Yes. A connection can belong to the whole company or to a single Space, and its tools are granted to that Space's Roles.
What you can do, within what you allowed when you connected it: read and change Tasks, read threads, search and edit the Library, and follow Runs.
Connect GitHub or one MCP server, grant the reads, and see the first report. Free during the open beta.