Your agent/Copilot Cowork

Copilot Cowork, with somewhere to publish.

A plugin your admin uploads once. After that, Cowork can put what it built online at a real address, instead of leaving another file in another folder.

Everything Cowork makes ends up as a file in a folder.

Which is fine for a document, and wrong for everything else. The dashboard, the calculator, the handbook, the little internal tool: those want an address people can open, not an attachment that goes stale the moment someone edits their copy of it.

The agenthost plugin gives Cowork the other half. It adds a connector and a skill: the connector is the agenthost MCP server, and the skill teaches Cowork the deploy workflow, so it knows what agenthost expects without anyone writing a prompt about it. Ask for the work and the link in the same instruction and you get both.

There is no API key anywhere in this. agenthost registers its own client with Cowork automatically, so the only credential involved is your own browser sign-in, once. And because everything is hosted in the EU by a European company, the answer to where the files went is short.

You ask for it in a sentence.

There are no commands to learn on our side. These are whole sentences, typed the way you would say them to a person, and each one is a thing agenthost does.

publish that as an internal page

Puts it online at a real address, and can lock it to the people you name so it never leaves the company.

the figures changed, republish it

Replaces the live version at the same address, so the link you circulated still works.

make it a proper tool, not just a page

Deploys something that runs, with a database attached, so it can remember what people enter.

put it on our own domain

Adds the domain and tells you the one record for IT to create. The certificate is handled here.

who has access to it?

Lists everyone invited, and takes someone off the list when they move on.

There is more of this in the how-to guides, which are written for your agent to read as much as for you.

Whatever it built, it can publish.

You do not have to know what it is made of. Your agent works that out and tells us.

  • framework preset
  • build command
  • output directory
  • install command
  • API keys
  • credit card
  • region

Nothing here can stop and ask you a question.

Every one of these is a setting some other host would demand before it would take your files. None of them exists here, which is why your agent can go from a folder to a working link without checking in.

  • Dockerfiles
  • port settings
  • TLS certificates
  • DNS records
  • CI pipelines
  • health checks
  • scaling rules

The one thing agenthost does expect is an entrypoint per runtime, and the deploy reference is where Copilot Cowork reads it before the first deploy.

How it connects.

Cowork plugins are installed by an administrator, so this one is a package you upload rather than an address you paste. It is built from an open repository, so you can read exactly what is in it first.

Download the plugin package ↗

Source, build script and release history are on GitHub. MIT licensed, and it is the same package we publish.

1

Download the package

One zip, attached to the latest release. It contains the agenthost connector, the deploy skill and the app manifest, and nothing else.

2

Upload it to your tenant

In the Microsoft 365 admin center, go to Manage apps, then Upload custom app, and pick the zip. Your admin does this once for everybody.

3

Install it in Cowork

It then appears under Sources and Skills, in Plugins, on the Discover tab. Installing it prompts the agenthost sign-in, which happens once in your browser.

Want to try it before involving IT? The repository has the sideload command for a personal install. The get started page walks through all of it, with the buttons and the sign-in step.

The usual ones.

What exactly does the plugin add?

Two things. A connector to the agenthost MCP server, which is what gives Cowork the ability to create projects and deploy, and a skill called deploy-on-agenthost, which teaches Cowork the workflow so it does not have to guess. The tool list itself is discovered from the server at runtime rather than fixed in the package.

Is there a key or secret for our admin to configure?

No. agenthost supports dynamic client registration, so Cowork creates its own OAuth client when the plugin is installed. Each person signs in once in a browser, and nobody ever handles a credential.

Can we see what is in the package before we upload it?

Yes. The plugin is open source and MIT licensed, the release is built automatically from a tag, and the build script is in the repository if you would rather assemble the zip yourself.

Where does the data go?

To the EU. agenthost is run by a European company, and your files, your database and your logs stay here. So does the billing.

Our privacy policy →

Does the same plugin work anywhere else?

Yes. The repository is also a Claude Code and Cursor plugin, so the same skill and the same connector can be installed there. If you only want the connector, those clients can add the agenthost server directly instead.

Every client, side by side →

Is there an API key to paste anywhere?

No. agenthost signs you in through your browser, and your agent never sees a password or a key. There is nothing to copy out of one window and into another, and nothing to rotate later.

What does it cost to try?

Nothing, and there is no card. Your first ten websites are free and stay free. You only pay when the thing you built has to run code on our side, or when you want it on your own domain.

What it costs →

Can I connect more than one agent to the same account?

Yes, as many as you like. They all see the same projects, so you can build something in one and update it from another. Connecting the second one is a single click, because your browser is already signed in.

Where is this actually hosted?

In the EU, by a European company. Your files, your database and your logs stay here, and so does the billing.

Not what you use?

agenthost is a standard remote MCP server, so anything that speaks MCP can drive it. These are the ones with a page of their own.

Point Copilot Cowork at it.

One package, uploaded once, and everything Cowork builds can have an address of its own.