Bring permitted field information into the assistant your team uses
Your team may already use an AI assistant to discuss plans or prepare questions. Sensorius is preparing access through MCP, a protocol that connects an AI assistant to external data. A supported assistant would be able to read only the field and device information your account is allowed to see. The aim is to let your team use relevant Sensorius information in the assistant it has chosen. **Preparing controlled early access:** compatibility, the permitted data and connection details must be confirmed by Sensorius. The planned connection is read-only, within the authenticated user's organisation and permissions.
Field Data in AI Assistants through MCP
Connect a familiar conversation with farm information
An external assistant often starts with whatever someone copies into the conversation. That can leave the source, date or field unclear. The planned connection would let a supported assistant read permitted field information from Sensorius.
Start with what the assistant needs to know to help with your question. A question about upcoming work may need the crop timeline, available forecast and recent operations. A question about a device may need its supported measurements or state. Access will depend on the validated client, available tools and the user's rights, rather than opening every record to every assistant.
Choose the task before the connection
A practical integration starts with a farm task your team already recognises. You might want to discuss a field's current context in your chosen assistant or prepare questions for an agronomist using permitted records. Define that task before deciding which data should be made available.
That gives us a specific use to discuss for early access. It also helps identify when a source is missing or a different service would be more appropriate. The integration is designed to make supported information available for consultation. It does not establish the assistant's agronomic qualification or guarantee the quality of every answer it produces.
Keep the connection within your team's permissions
The planned connection is tied to an authenticated user, their organisation and their allowed data access. The assistant should receive only the information the user is permitted to read. Early access requires a supported sign-in and authorisation process, your consent, and a way to withdraw access.
Before activation, Sensorius must confirm the supported client and access details. Your organisation should also agree who may connect an external assistant and what information may be used there. An assistant provider may process data under its own terms. Those terms and your organisation's privacy requirements need review alongside the Sensorius connection.
Understand the read-only boundary
Reading information about a field is different from changing how its equipment operates. The planned customer MCP connection reads supported field and device information. It does not send irrigation commands, change device settings, save a timeline or perform automatic field actions.
Your devices continue to send their supported information to the Sensorius Platform. The external assistant connects to Sensorius through MCP; it does not connect directly to the physical device. Where remote control is available, an operator uses the separate supported interface and the installation's safety and confirmation procedure.
Use the right advisory service for the situation
Sensorius Agronomic Adviser is the built-in adviser for field questions. Field advisor helps prepare a crop timeline after the user's review and confirmation. Customer MCP access is a separate, planned option for connecting a supported external assistant.
These services may be useful to different teams. You can discuss whether the built-in adviser already meets the need or whether a familiar external assistant serves a specific purpose. Early-access planning starts with the information needed for that task. The farm remains responsible for decisions made from the resulting conversation.
Make sources part of the conversation
Field information changes with time. A reading, forecast or operation record needs its date and context to be useful. The early-access requirements call for the assistant to receive supported data with a clear indication of whether it is current, incomplete, out of date or unavailable. Missing information must not be invented.
That is a product requirement. It does not mean every assistant can connect today. Before an integration is offered, Sensorius must demonstrate the supported connection and its data boundaries. Your team can then assess whether the information is suitable for the task and whether the assistant presents its sources clearly enough for a farm discussion.
Prepare a focused early-access request
Tell us which assistant your team uses, who needs access and the field question it should support. Identify the relevant records and any restrictions your organisation places on external processing. We can discuss client compatibility and the current state of the planned service.
MCP access is not yet presented as a self-service connection for every assistant. Before use, we need to agree availability, support and how to activate the connection. Claims that the integration reduces administration time or costs need their own measured evidence; a working connection alone would not establish those results.
Two examples of a possible early-access question
These scenarios illustrate the intended read-only use. They are not customer results and do not confirm that any particular client is currently supported.
Discuss a change in field measurements
A farm manager asks a supported assistant to explain how recent field measurements have changed. If the assistant is included in early access and the user permits it, it could read available measurements and relevant field context, retaining dates and any limits in its response.
The manager checks the information in Sensorius and discusses the field question with an agronomist. The assistant does not inspect the crop or choose an operation. It can only read information available to the user.
Prepare questions for a season review
Before a season review, a team member asks a supported assistant to gather available field records, measurements and timeline information into questions for the meeting. The assistant should show which periods and fields the information covers and where records are missing.
The team reviews those questions with its agronomist and checks records in Sensorius. The assistant does not add a field action or make a change in the platform; the farm team decides what to follow up.
Connect a familiar conversation with farm information
An external assistant often starts with whatever someone copies into the conversation. That can leave the source, date or field unclear. The planned connection would let a supported assistant read permitted field information from Sensorius.
Start with what the assistant needs to know to help with your question. A question about upcoming work may need the crop timeline, available forecast and recent operations. A question about a device may need its supported measurements or state. Access will depend on the validated client, available tools and the user's rights, rather than opening every record to every assistant.
Choose the task before the connection
A practical integration starts with a farm task your team already recognises. You might want to discuss a field's current context in your chosen assistant or prepare questions for an agronomist using permitted records. Define that task before deciding which data should be made available.
That gives us a specific use to discuss for early access. It also helps identify when a source is missing or a different service would be more appropriate. The integration is designed to make supported information available for consultation. It does not establish the assistant's agronomic qualification or guarantee the quality of every answer it produces.
Keep the connection within your team's permissions
The planned connection is tied to an authenticated user, their organisation and their allowed data access. The assistant should receive only the information the user is permitted to read. Early access requires a supported sign-in and authorisation process, your consent, and a way to withdraw access.
Before activation, Sensorius must confirm the supported client and access details. Your organisation should also agree who may connect an external assistant and what information may be used there. An assistant provider may process data under its own terms. Those terms and your organisation's privacy requirements need review alongside the Sensorius connection.
Understand the read-only boundary
Reading information about a field is different from changing how its equipment operates. The planned customer MCP connection reads supported field and device information. It does not send irrigation commands, change device settings, save a timeline or perform automatic field actions.
Your devices continue to send their supported information to the Sensorius Platform. The external assistant connects to Sensorius through MCP; it does not connect directly to the physical device. Where remote control is available, an operator uses the separate supported interface and the installation's safety and confirmation procedure.
Use the right advisory service for the situation
Sensorius Agronomic Adviser is the built-in adviser for field questions. Field advisor helps prepare a crop timeline after the user's review and confirmation. Customer MCP access is a separate, planned option for connecting a supported external assistant.
These services may be useful to different teams. You can discuss whether the built-in adviser already meets the need or whether a familiar external assistant serves a specific purpose. Early-access planning starts with the information needed for that task. The farm remains responsible for decisions made from the resulting conversation.
Make sources part of the conversation
Field information changes with time. A reading, forecast or operation record needs its date and context to be useful. The early-access requirements call for the assistant to receive supported data with a clear indication of whether it is current, incomplete, out of date or unavailable. Missing information must not be invented.
That is a product requirement. It does not mean every assistant can connect today. Before an integration is offered, Sensorius must demonstrate the supported connection and its data boundaries. Your team can then assess whether the information is suitable for the task and whether the assistant presents its sources clearly enough for a farm discussion.
Prepare a focused early-access request
Tell us which assistant your team uses, who needs access and the field question it should support. Identify the relevant records and any restrictions your organisation places on external processing. We can discuss client compatibility and the current state of the planned service.
MCP access is not yet presented as a self-service connection for every assistant. Before use, we need to agree availability, support and how to activate the connection. Claims that the integration reduces administration time or costs need their own measured evidence; a working connection alone would not establish those results.
Common questions
Can we connect our assistant today?
Customer access is being prepared as controlled early access. Sensorius must confirm the client and supported information before activation. The page does not promise general availability or a release date.
What information is intended to be available?
The planned scope covers permitted field and device information through validated read-only tools. The actual set depends on the supported client, tool availability and the authenticated user's permissions.
Can the assistant operate irrigation equipment?
No. Customer MCP access is read-only. Remote equipment commands are a separate operator action through the supported Sensorius interface and a correctly commissioned installation.
Does this replace the Sensorius Agronomic Adviser?
It provides a different integration option. The built-in adviser supports consultations within Sensorius; planned customer MCP access would let an approved external assistant read permitted information for its own conversation.
Who needs to approve a connection?
Sensorius confirms product compatibility and the supported connection. Your organisation must agree the user, data scope and external-provider terms. Security and privacy must be reviewed before activation.
Tell us what you want to connect
Share the assistant or MCP-compatible client your team uses, the field questions you want to explore and the users who would need access. Sensorius can discuss the planned early-access scope and confirm what is supported when the validation work is complete.
Ask about Sensorius MCP early access
Agronomic Adviser · MCP early access on the Platform page
A planned connection to permitted field information
Planned MCP read access to permitted field data.
External assistantActivation requires supported sign-in, consent, and access checks.
Access permissionsEquipment commands remain outside the planned read-only connection.
Read-only accessConnect a familiar conversation with farm information
An external assistant often starts with whatever someone copies into the conversation. That can leave the source, date or field unclear. The planned connection would let a supported assistant read permitted field information from Sensorius.
Start with what the assistant needs to know to help with your question. A question about upcoming work may need the crop timeline, available forecast and recent operations. A question about a device may need its supported measurements or state. Access will depend on the validated client, available tools and the user’s rights, rather than opening every record to every assistant.
Keep the connection within your team's permissions
The planned connection is tied to an authenticated user, their organisation and their allowed data access. The assistant should receive only the information the user is permitted to read. Early access requires a supported sign-in and authorisation process, your consent, and a way to withdraw access.
Before activation, Sensorius must confirm the supported client and access details. Your organisation should also agree who may connect an external assistant and what information may be used there. An assistant provider may process data under its own terms. Those terms and your organisation’s privacy requirements need review alongside the Sensorius connection.
Understand the read-only boundary
Reading information about a field is different from changing how its equipment operates. The planned customer MCP connection reads supported field and device information. It does not send irrigation commands, change device settings, save a timeline or perform automatic field actions.
Your devices continue to send their supported information to the Sensorius Platform. The external assistant connects to Sensorius through MCP; it does not connect directly to the physical device. Where remote control is available, an operator uses the separate supported interface and the installation’s safety and confirmation procedure.
Common questions
Can we connect our assistant today?
Customer access is being prepared as controlled early access. Sensorius must confirm the client and supported information before activation. The page does not promise general availability or a release date.
What information is intended to be available?
The planned scope covers permitted field and device information through validated read-only tools. The actual set depends on the supported client, tool availability and the authenticated user's permissions.
Can the assistant operate irrigation equipment?
No. Customer MCP access is read-only. Remote equipment commands are a separate operator action through the supported Sensorius interface and a correctly commissioned installation.
Does this replace the Sensorius Agronomic Adviser?
It provides a different integration option. The built-in adviser supports consultations within Sensorius; planned customer MCP access would let an approved external assistant read permitted information for its own conversation.
Who needs to approve a connection?
Sensorius confirms product compatibility and the supported connection. Your organisation must agree the user, data scope and external-provider terms. Security and privacy must be reviewed before activation.
Tell us what you want to connect
Share the assistant or MCP-compatible client your team uses, the field questions you want to explore and the users who would need access. Sensorius can discuss the planned early-access scope and confirm what is supported when the validation work is complete.
Ask about Sensorius MCP early access
Agronomic Adviser · MCP early access on the Platform page
Related solutions and product information
See the Agronomic Adviser, the Platform's MCP early-access section and agronomic advice. All Sensorius solutions.
Discuss the assistant and farm task you have in mind
Bring a specific use of field information and the assistant your team wants to connect. We can explain the current preparation, compatibility checks and next steps for early access.
Ask about Sensorius MCP early accessDiscuss the assistant and farm task you have in mind
Bring a specific use of field information and the assistant your team wants to connect. We can explain the current preparation, compatibility checks and next steps for early access.
Ask about Sensorius MCP early accessPowiązane rozwiązania i informacje o produkcie
Zobacz Agronomic Adviser, wczesny dostęp MCP na stronie Platformy i konsultacje agronomiczne. Wszystkie rozwiązania Sensorius.
Omów asystenta i zadanie gospodarstwa
Przygotuj konkretne zastosowanie danych i nazwę asystenta, którego chcecie połączyć. Wyjaśnimy stan przygotowania, sprawdzenie zgodności i kolejne kroki wczesnego dostępu.
Soluções e informação de produto relacionadas
Consulte o Agronomic Adviser, acesso antecipado MCP na plataforma e aconselhamento agronómico. Todas as soluções Sensorius.
Discuta o assistente e a tarefa que tem em mente
Traga uma utilização específica dos dados e o assistente que pretende ligar. Explicamos a preparação atual, verificações de compatibilidade e próximos passos para acesso antecipado.
Soluciones e información relacionadas
Consulta Agronomic Adviser, acceso anticipado MCP en Platform y asesoramiento agronómico. Todas las soluciones Sensorius.
Comenta el asistente y la tarea que tienes en mente
Trae un uso específico de datos y el asistente que quieres conectar. Explicaremos preparación actual, comprobaciones y próximos pasos.
Discuss the assistant and farm task you have in mind
Bring a specific use of field information and the assistant your team wants to connect. We can explain the current preparation, compatibility checks and next steps for early access.
Ask about Sensorius MCP early access