AI, MCP and CLI

Use Canopy from the AI you already have.

Your team will end up with an assistant in every tool they open. We are not selling you another one. Canopy has an assistant built in, and the same operation is open to the assistant you already use, turning what is happening into decisions and work that gets done.

Canopy sits at the center. Your assistant reaches it through MCP: Microsoft Copilot, Claude, ChatGPT, Gemini, Codex, Cursor. Your business systems connect through integrations: Dynamics 365 (Business Central), Microsoft Teams (Alerts and updates), Slack (Alerts and updates), Webhooks (Your own tools), and more as you need them. Your own systems use the API and the command line. Canopy turns it all into decisions (priorities for today, crew plans) and actuation (tasks dispatched, irrigation runs), within your roles and permissions.

Works with

The assistant your team already uses.

If your team's assistant can add connectors, it can use Canopy. Nobody has to learn a new tool, and nobody in the office needs to be a software expert to set it up.

  • Microsoft Copilot
  • Claude
  • ChatGPT
  • Gemini
  • Codex
  • Cursor
Up to date with the standard
Built on the current version of MCP, the open standard the major assistants use to connect to other software.
Nothing to install
Canopy runs in the cloud. Adding it to an assistant means pasting one web address.
Sign in, no passwords shared
People sign in with their Canopy account. The assistant never sees a password, and there are no keys to copy around.
Same access as the person
The assistant sees and does only what that person can in Canopy. Their role carries over.
Switch it off any time
Disconnect in the assistant, or remove the person in Canopy, and access ends right away.
Only your data
Each organization's records are kept separate, and every connection is encrypted.

Product names and logos belong to their owners and are shown only to say the product can connect to Canopy.

Our position

Not another layer. The record underneath.

Built in, not bolted on
The assistant inside Canopy works from the same records and permissions as the screens. There is nothing separate to buy, sync or keep in step.
Your assistant, your choice
If your team already lives in another assistant, connect Canopy to it. You sign in once with your Canopy account, the assistant gets your access and no more, and you can withdraw it at any time.
Every action is operations work
Dispatching a crew, logging hours and starting an irrigation run are all decisions the operation makes every day. Whoever makes them, a person, a schedule or an assistant, they follow the same roles and permissions.
The assistants a team already has sit on top. Canopy sits underneath them as the record of what ran, what the crew did and what happens next, which any of them can use.

Ways in

One operation, reached the way your team works.

Inside Canopy

Ask about your operation from inside the app. The assistant works from the same records and the same permissions as the screens you already use, so it never sees more than you can.

Nothing to install.

From your assistant

Add Canopy to the assistant your team already uses and ask in the conversation you already have open: hours the crew logged this week, which blocks are behind, what to schedule tomorrow.

Microsoft Copilot (through Copilot Studio), Claude, ChatGPT, Gemini, Codex, Cursor or any assistant that can add connectors.

From your own systems

Feed Canopy into the reports and tools your team builds itself, or script routine work from the command line. An administrator issues the keys from inside Canopy.

An API key from your administrator, or the Canopy CLI.

Connected to your business systems

Canopy connects to the systems you already run: Dynamics 365 Business Central for ERP records, Microsoft Teams and Slack for alerts and updates, and webhooks for anything else. More are added as customers need them.

An administrator connects each one from the Integrations page in Canopy.

How a question travels

Every request is checked, every time.

The first time, you sign in on a Canopy page with the account you already use. Your password never reaches the assistant, and disconnecting takes effect immediately. How the connector works

  1. You ask your assistant how many hours the potting crew logged this week.
  2. The assistant asks Canopy, as you, using the access you granted when you signed in.
  3. Canopy checks who is asking, which organization they belong to and what their role allows.
  4. Canopy reads that organization's labor records and nothing else.
  5. The records go back to the assistant, which answers in plain language: the hours, and how they compare with the standard.

From question to action

Every action follows your permissions.

  1. Ask

    • Hours the potting crew logged this week
    • Which blocks are behind on spacing

  2. Decide

    • Tomorrow's crew plan
    • What to move up the list

  3. Act

    • Dispatch the spacing crew
    • Log the hours
    • Start an irrigation run

Canopy treats an irrigation run like dispatching a crew: a decision, made by someone with the right role, with confirmation where it matters.

Try it on your own operation.

We are working with a small group of growers in early access. Tell us which assistant your team uses and we will set you up.

Ask for early access How the connector works