Autonomous MCP

Stop explaining.
Let it do the work.

Give ChatGPT your computer and it handles the rest. Anything you would sit down and do yourself, it does. You just say what you want.

ChatGPT
→
Autonomous MCP
→
your computer

01 / work

Ask for the outcome, not the instructions.

These are ordinary requests. The difference is that ChatGPT can actually reach the machine where the work exists.

Rename these 400 photos by the date they were taken.

It reads the metadata, applies the same rule to every file, and finishes the batch on your computer.

Clear the duplicates out of my downloads.

It searches the folder, compares what it finds, and can clean the duplicates after you confirm.

Find the contract I signed in March and pull out the dates.

It searches inside your local files, opens the relevant document, and returns the answer in ChatGPT.

Set this project up and get it running.

It can inspect the repo, install what is missing, run the project, read the error, and try again.

02 / setup

Three pieces. One connection.

The local client stays isolated on your machine. The backend authenticates and routes calls. ChatGPT remains the interface.

1

Create the account

Your account owns the paired machines, OAuth connections, plan and quota.

2

Install and pair the client

The client opens an outbound connection. Nothing needs to listen publicly on your computer.

$ npm install -g autonomous-mcp
3

Connect ChatGPT

Add the MCP URL from your dashboard, approve OAuth once, then use normal messages.

03 / boundaries

The useful part is local. So are the boundaries.

The agent checks the machine, path and command before work runs. The server cannot silently turn another account into yours.

01

Folder scope

Limit the client to the directories you choose. Real paths are resolved before a file action runs.

02

Command policy

Blocked commands are rejected locally, including when they are hidden in chained shell syntax.

03

Account isolation

A device belongs to one account. Calls cannot be dispatched to a machine owned by another account.

04

Outbound only

The client connects out to the service. Pairing does not open an inbound port on your computer.

04 / plans

Limits that match how people actually use it.

A plan can combine rolling windows. Five hours, one week, thirty days, or any other configured period can coexist.

Free 1,000 / 30 days
Pro 30,000 / 30 days
Power 250,000 / 30 days
Business 1,000,000 / 30 days

New accounts start on Free. Your dashboard shows every active window and when capacity returns.

Coming next

The computer becomes optional.

Today the agent runs on a machine you already own. The next step is the same interface with a hosted machine behind it.

Your own computerrequired
Keep it awakerequired
Local installrequired
Use it from your phonesame flow

05 / questions

The things worth knowing before you connect a machine.

Do I need to know how to program?
No. There is one installation step on the computer. After that you use normal ChatGPT messages.
Does my computer have to stay on?
Yes. The agent has to be running and the computer has to be reachable. A cloud computer option is planned.
Can it change or delete my files?
Yes, inside the folders you allow. The local agent also applies path and command policies before an action runs.
Can more than one computer be connected?
Yes. If several machines are online, ChatGPT can target the one you name.
Does it work on Windows and Mac?
Yes, and Linux. The current client requires Node.js 20.11 or newer.
What if I change my mind?
Unpair the computer or stop the agent. Its device credential stops being useful after unpairing.

Your computer. ChatGPT's hands.

Pair one machine, connect ChatGPT, and give it a real task.