Live · 43 ready-made apps · 673 connectors

Tools don't run a business.
Apps do.

Everyone else gives your AI tools. Uniwork gives it the apps a company is actually run on — installed, connected to each other, every one an MCP server. It installs what it needs, builds what doesn't exist yet, and works across all of it under your permissions.

Headless
set up https://uniwork.ai/SKILL.md

Hosted claude.ai and ChatGPT connectors are coming — they sign in with OAuth, which we're finishing.

and let it take it from there.

Uniwork
CRMpipeline & contacts
Invoicesbilling
Projectsdelivery
HR Managerpeople
Help Desktickets
Knowledge Basedocs
Formsintake
Roadmapfeedback
Campaignsemail & sequences
Commercestorefront
Expensesspend
Hiringcandidates
Incidentson-call
Analyticsdashboards
Timesheetshours
Proposalssignatures
Schedulerbookings
Vendorssuppliers
Websitepublic pages
Your own appdescribe it

Forty-three ready-made apps are the starting point, not the catalogue: install them, reshape them, or describe the one nobody sells and get it built. Every app is its own MCP server, and 673 connectors reach the SaaS you keep.

What it can do

Not a toolbox. A business it can run.

Install what it needs

It browses the store and installs an app — or a whole starter pack for your kind of business, in the right order, resumable. The apps arrive connected, seeded and permissioned.

Start the app nobody sells

Nothing fits? It creates a new app in your workspace and hands App Studio the brief — the data model, screens and automations get built out while you watch, then it's yours.

Work across apps, with no glue

Log time in Timesheets and Invoices raises the invoice, then takes the number back. Proposals pulls the deal, company and contact from CRM in one hop. The finance dashboard reads Invoices and CRM live. Each app declares what it may read and the owner consents — your agent isn't the integration.

Leave it running

What shouldn't need asking twice becomes an automation it writes, deploys and runs — on a schedule, an inbox, a webhook or an event — with approvals where a human should still say yes.

Four endpoints, 64 platform tools, and every installed app its own MCP server — 2,400+ tools across the suite. initialize and tools/list answer without a token, so your client can look before anyone signs in.

Three ways in

Same apps. Same permissions. Same data.

Whichever one you speak. The UI is not a different product — it is the third door into the same platform.

Skill

Hand your agent one URL. It reads SKILL.md, walks the sign-in itself, adds the server and starts working. Nothing to configure by hand.

Read SKILL.md →

MCP

JSON-RPC over HTTP. Your own uat_ token, 90 days, revocable — the agent acts as you and sees exactly what you see.

The UI

The same apps with screens on them, for the people who would rather click — and UniAgent in the sidebar for the ones who would rather ask.

Open Uniwork →

1 · Sign in

You need a Uniwork account. The agent acts as you — it sees what you see, and no more.

Sign in →

2 · Approve it once

Your agent opens a consent screen; approve it and it keeps a token starting uat_. Ninety days, revocable on the spot under Settings → Security.

3 · It takes over

It discovers the tools itself. Hosted claude.ai and ChatGPT connectors are coming — they sign in with OAuth, which we're finishing; Claude Desktop, Claude Code and Cursor work today.

Bring your agent. We'll bring the business.

Private beta is open to a small group of teams. Your AI client comes along for free.