Key Takeaways
- AROYA’s new connector integrates with ChatGPT or Claude, allowing commercial cannabis cultivation teams to query facility data in plain language.
- The connector retrieves specific information like daily reports, irrigation history, and sensor readings directly from AROYA’s existing system.
- It is read-only, meaning it does not change settings or execute commands and requires users to interpret the results responsibly.
- Growers can explore various questions, improving workflow by making data retrieval quicker and more efficient.
- Setup involves connecting AROYA as a custom connector, with an introductory free period available for users.
Commercial growers can now question their own facility data in plain language, bringing another way to investigate what is happening in the grow.
A cultivation team can collect useful data all day and still spend too much time getting an answer to a straightforward question. Comparing rooms means finding the right readings. Investigating a dryback means checking what happened around it. Preparing for a morning walkthrough can involve enough screen time to delay getting into the facility itself.
AROYA’s new connector gives commercial cannabis growers another way into that information. Released October 13, the integration connects an existing AROYA account with ChatGPT or Claude, allowing users to ask about their own cultivation operation in plain language. The assistant can retrieve relevant records and organize a response around the question being asked.
For growers already using one of those tools, the appeal is concrete: bring actual facility data into the conversation. Instead of discussing a hypothetical grow, they can investigate the rooms and production history they already manage. How useful that becomes depends on the questions they ask and what they do with the answers.
From Collected Readings to a Working Conversation
AROYA combines substrate and climate sensors with crop steering software for commercial cultivation. Its platform gives operators a way to measure conditions and connect those observations with how they run a crop. The company is a business unit of Addium, whose measurement work spans agriculture and food science.
The connector adds a different interface to the information already in that system. A grower can request a daily facility report before walking rooms, compare average electrical conductivity and substrate moisture across the past week, or pull irrigation events associated with a period of dryback. Those are questions grounded in the operation’s own records.
The technology behind the connection is Model Context Protocol, or MCP. In this application, it gives an AI assistant a route to retrieve authorized AROYA information. Growers do not need to build their own integration to use the hosted connector. They connect their accounts, then direct the conversation toward the issue they want to investigate.
AROYA is clear about where its role ends. The company supplies the connection to cultivation records; the reasoning comes from the grower’s chosen assistant and model. That distinction helps explain both the flexibility of the tool and why a response still needs someone qualified to evaluate it.
“The only thing our product does here is connect an AI agent to the data and point it at the right place,” Jason Van Leuven, AROYA’s Director of Applied Technology, said in the company’s launch announcement. Van Leuven built the connector and ran its beta program.
Questions That Belong in a Cultivation Operation
The strongest starting point is a question that already comes up during the workday. A cultivation director preparing for a meeting may want a concise facility overview. Someone responsible for irrigation may need a closer look at events before a particular dryback. An operator comparing production cycles may want records from two runs of the same cultivar placed alongside each other.
AROYA lists each of those among the connector’s applications. Users can also investigate sensor health, including devices with unstable connections. That is useful context when a team is trying to understand what its records actually show before drawing a cultivation conclusion from them.
Consider a grower reviewing moisture behavior after an unexpected change. Asking for irrigation events over a defined period gives the assistant a bounded task. A follow-up can ask it to arrange the findings into a table, making the sequence easier to review. The grower can then decide which part of the record deserves a closer look.
That example describes a workflow, not a diagnosis. An organized account of events can support an investigation without proving why something happened. The difference matters in a room full of living plants, where a plausible explanation still has to survive contact with the crop.
Comparisons offer another practical entry point. A team running the same cultivar across facilities can ask the assistant to bring relevant records together for review. Having information in one conversation can help people develop better follow-up questions, while the interpretation remains tied to their knowledge of each site and production cycle.
Reports Built Around the Task
The connector is designed to support requests beyond a fixed menu of scripted questions. According to AROYA’s announcement, users can reach nearly everything available to them in the app, including sensor readings, irrigation history and harvest groups. They can also ask for exports in a preferred format.
That flexibility matters because different people need different levels of detail. A cultivation lead may want a short morning overview before heading into the rooms. The person investigating a specific issue may need a longer report with the relevant measurements. An executive reviewing operations may need a comparison that makes the underlying differences easier to discuss with the cultivation team.
The same information can serve those jobs without every reader having to work through the same presentation. Users can specify the format they want and refine it through follow-up requests. A concise answer can become the starting point for a deeper review, rather than the end of the investigation.
For an established team, a sensible first use is a recurring question that already takes time to answer. Working through that task gives the operator a basis for judging whether the connector improves the process. It also keeps evaluation focused on an actual need instead of an impressive demonstration with little connection to daily work.
The Grower Stays Responsible For the Decision
The current integration is read-only. It cannot change facility settings or carry out cultivation commands. A request for information does not become an instruction to adjust the environment, and access remains governed by the user’s existing AROYA permissions.
That boundary separates this release from the broader idea of an AI system operating a facility. The connector helps a person retrieve and examine information. Acting on it remains a human responsibility, with the same need for sound cultivation judgment that existed before the conversation started.
AROYA’s documentation also acknowledges that an assistant can interpret a question incorrectly or reach an unsupported conclusion. Important findings should be checked against the app before someone acts on them. Faster retrieval does not make every explanation correct.
Philip Malmquist, Director of AROYA, addressed the adoption question directly in the launch announcement: “If you plug it in and change nothing, nothing changes.” The comment puts the value of the release where it belongs: in the working habits of the people using it.
An operation has to decide where the tool fits. If the team identifies a useful question, checks the response and incorporates what it learns into an existing review process, there is a practical basis for evaluating the integration. Merely adding another connection to an account does little on its own.
Getting an Existing AROYA Account Connected
Setup involves adding AROYA as a custom connector in a supported ChatGPT or Claude account and signing in with the user’s AROYA credentials. Facility access must be enabled, and organization-managed AI accounts may also require administrator approval. AROYA provides setup instructions for both assistants.
The connection follows the facilities and information that login is already permitted to access. Growers should check the current plan requirements and setup guidance for their chosen assistant before starting. Those instructions are a better reference for account-specific details than a general article about the release.
AROYA is offering the connector during an introductory free period. Operators can confirm availability and future renewal terms with their account manager while determining how it fits their facility. Existing subscribers have a direct way to explore the connection using information they already collect.
For commercial cannabis growers, the useful question is how much work sits between a measurement and an informed decision. This release addresses the retrieval and reporting portion of that process. A team can ask about its own operation, inspect the answer and spend its attention on what deserves action.
Explore AROYA’s ChatGPT and Claude integration, see the setup resources or request a demonstration at AROYA’s artificial intelligence page.
Sponsored content produced in partnership with AROYA.
Frequently Asked Questions
AROYA is a commercial cannabis cultivation platform built by Addium that combines substrate and climate sensors with crop steering software, giving operators a data-driven way to measure grow conditions and manage production. Its new ChatGPT and Claude connector — released October 13 — lets growers query that facility data in plain language directly through either AI assistant.
The integration works through Model Context Protocol (MCP), which gives a connected AI assistant an authorized route into a grower’s existing AROYA records — irrigation history, sensor readings, harvest groups, and more. It’s read-only by design and never changes a facility setting, meaning growers can ask questions and inspect answers without the system acting on anything. You can explore the full setup and request a demo at AROYA’s artificial intelligence page.
Asking AROYA through ChatGPT or Claude gives commercial cannabis growers a direct answer to a specific question — without opening dashboards, scrolling through graphs, or cross-referencing multiple screens. Instead of decoding a visual, a grower types the question and gets the relevant records organized around it. One MSO grower in California reported getting back roughly two hours a day from that shift alone.
Manual graph review puts the retrieval burden on the person doing the reviewing — finding the right room, the right time window, the right sensor. The AROYA AI integration handles the retrieval and reporting portion of that process, so attention can go toward evaluating the answer rather than hunting for the data. The grower still makes every decision; the tool just stops making information hard to reach.
Commercial cannabis growers should use AROYA’s AI connection because it eliminates the gap between collecting cultivation data and actually using it to make decisions. Instead of navigating dashboards to piece together an answer, growers can ask about their own facility in plain language and get a structured, relevant response built around the question they actually need answered.
The value isn’t in the technology itself — it’s in what it gives back. One MSO grower in California reported reclaiming two hours a day from manual data retrieval. Cory, Head Grower at Harbor House Collective, put it plainly: “It helps you understand the root cause of your successes.” That kind of insight doesn’t come from faster graphs — it comes from asking better questions of data you already own.
No — the AROYA MCP connector is read-only. It cannot change facility settings, adjust environmental controls, or issue cultivation commands. Access to your cultivation data is governed entirely by your existing AROYA account permissions, meaning the same role-based controls that determine what you can see in the app apply to the AI connection as well.
Facility administrators must enable access before any connection is active, and organization-managed AI accounts may also require administrator approval before a user can query data through ChatGPT or Claude. Your data never leaves the boundaries of what your login is already authorized to access — the assistant retrieves information from your own AROYA records and nothing more. You can learn more about how the integration works at AROYA’s artificial intelligence page.
You connect AROYA to Claude or ChatGPT by adding it as a custom connector inside your chosen assistant and signing in with your existing AROYA credentials. Before you start, give your facility admin a heads-up — they need to enable access at the facility level first, and organization-managed AI accounts may also require administrator approval before the connection goes live.
Once you’re connected, just ask about your operation the same way you’d phrase it to a teammate. Questions like “which room ran warmest overnight” or “did every zone get its first shot on time” are solid starting points. AROYA also lets you request data exports in formats like CSV or JSON, and you can refine the format through follow-up questions. Full setup guides and short video walkthroughs for both assistants are available at AROYA’s artificial intelligence page.
