Set up Croft in Microsoft Copilot.

1. Create an agent in Copilot Studio

1. Open Copilot Studio

   Go to copilotstudio.microsoft.com and sign in with your work account. Pick the environment you want the agent to live in.

2. Create a new agent

   Select Create → New agent. Give it a name like Croft and a short description — "Build and manage internal apps on Croft." You can skip the extra setup and go straight to the agent.

2. Add Croft as an MCP tool

1. Open Tools and add a new one

   On your agent, go to the Tools page, select Add a tool → New tool → Model Context Protocol. The MCP onboarding wizard appears.

2. Fill in Croft's details

   Server name: Croft.
   Server description: "Builds, deploys, and manages apps on the team's Croft server." Copilot uses this to decide when to call Croft, so keep it clear.
   Server URL: https://mcp.oncroft.net (copy your croft's exact link from the dashboard). Croft speaks the modern streamable transport Copilot Studio requires.

3. Set authentication to OAuth 2.0

   Choose OAuth 2.0, then Dynamic discovery — Croft supports it, so Copilot Studio finds the right endpoints and registers itself automatically. Select Create, then Next.

4. Create the connection and add it

   On Add tool, select Create a new connection, then Add to agent. Croft is now a tool your agent can use.

5. Give the agent its instructions

   In the agent's instructions, tell it what it's for — "Help teammates build and update apps on Croft. Use the Croft tool to create, deploy, and fix apps. Ask what they want, then build it." Test it in the Test pane: sign in to your croft when prompted, and try "build me a simple stocktake app."

3. Publish it to your whole team

1. Publish the agent

   Select Publish at least once. This makes the current version available to connect to Teams.

2. Add the Teams channel

   Go to Channels → the Teams and Microsoft 365 Copilot tile. Leave Make agent available in Microsoft 365 Copilot selected if you want it there too, then select Add channel.

3. Keep it inside your org

   Turn on the agent's security setting for end-user authentication so only people in your organisation can use it. Croft stays private either way — this just keeps the agent itself internal.

4. Submit it to everyone in your org

   Open Availability options, select Show to everyone in my org, then Submit for admin approval. Your Microsoft 365 / Teams admin approves it in the Teams admin center, and it appears in the Built for your org section of the Teams app store.

5. Pin it for everyone (optional)

   Ask your admin to use Teams app setup policies to auto-install and pin the agent, so it sits in everyone's app bar in Teams — no hunting required.