How to connect your farm data to ChatGPT and Claude

To connect your farm data to ChatGPT or Claude, you add a connector to the assistant — a bridge that lets it query your farm management system at the moment you ask — and sign in with your own portal account. At upCampo, the address is the same for both: https://mcp.upcampo.com.br/mcp. Once authorized, the assistant stops answering with generic information from the internet and starts answering with the numbers from your season, respecting exactly the permissions your user already has, farm by farm. This guide explains what changes in practice, what you can ask, what you can record, and how to set up the connection on both sides — including a configuration trap that has already broken the connection for two users.

What a connector is, in farm terms

On its own, an AI assistant knows a lot about agriculture and nothing about your agriculture. Ask how much it rained on field 12 in August and it will say it has no access to that — or, worse, it will guess. The connector closes that gap: it is an address you register once in the assistant that, from then on, lets it fetch the data at the source the moment you ask.

The standard behind it is called MCP, and it is open. It is not an exclusive integration with one app: it is the same plug Claude and ChatGPT adopted to connect to external systems, which is why upCampo has a single address that works for both. What matters for people on the farm is the result: there is no export and no spreadsheet in between, and the connector does not store the data. Every question is a live query against the system, with your login.

What changes when AI sees your real data

The difference shows up with the first question. Without a connector, “is my cost per hectare high?” returns a lecture on how farm costs are built. With a connector, it returns the list of your fields, with the figure for each one, in the current season.

Three practical changes appear right away:

• A question replaces the report. Much of what people ask the office for is a one-off lookup — how much of that product is left, which work orders are open, how much has been harvested in a sector. It becomes one sentence, with no filter to pick and no waiting for someone to run it.
• Cross-checking gets cheap. “Compare the rainfall of the last 30 days with planting progress by field” would take two screens and a spreadsheet in between. For the assistant, it is a single question.
• People who don’t use the system can see the farm again. The partner, the outside consultant, the controller’s office: people who won’t learn to navigate the portal but already talk to an AI every day. That is where the connector pays off most.

The limit is the same as on WhatsApp: the numbers come from your system, but the assistant writes the sentence. For season close, inventory counts, and final cost, the portal’s official report is still the document of record. The connector is for looking things up fast and deciding sooner, not for replacing the close.

What you can ask

There are twelve query tools covering day-to-day topics. In practice you don’t pick any tool: you write the question in your own words and the assistant decides where to look.

Topic	Sample question
Farms and seasons	Which farms and seasons do I have access to?
Production	What was the average yield per hectare for each soybean variety?
Rain and weather	How much did it rain on each field in the last 30 days?
Pest scouting	Which pests were above the action threshold in the latest scouting report?
Work orders	Which field work orders are still open, and what is the area of each?
Inventory	Which crop protection products are below minimum stock?
Fleet	What was the average fuel consumption of the tractors last month?
Post-harvest	How many bales were harvested this season, and what was the average yield?
Costs	What is the cost per hectare of each field this season?

Two of the twelve don’t query the farm: they search and read Help Center articles. “How do I register a new field?” also gets an answer — and that one doesn’t depend on permissions, because the documentation is public. If you have more than one farm, the assistant answers for your current farm; to ask about another, just name it in the question.

Each topic has a method behind it, and knowing it helps you read what comes back: pest scouting depends on the action threshold the farm has registered, cost per field depends on how work orders are allocated, and inventory depends on invoice entry and on stock being drawn down by applications. The assistant reads what is there; it does not fix incomplete records.

What you can record there

Besides the twelve queries, there are five entry tools: rainfall, fueling, work order execution, work order, and invoice entry. They are the same records UPí already handles on WhatsApp, now available in the assistant you use on your computer.

Two rules apply to all of them: the assistant summarizes what it is about to record and waits for your confirmation, and recording requires its own permission, separate from query permission and granted per farm. If the permission is missing, it tells you which one and saves nothing.

And there is a deliberate absence: none of the seventeen tools deletes data. There is no delete function in the connector. The worst case of a mistake is one extra entry, which you fix in the portal — never a lost record.

Before you connect: three prerequisites

Check these three conditions before opening the assistant’s settings. The third is the one usually missing.

1. UPí under contract. The connector is part of it, and it is contracted separately from the other modules. The terms are on the pricing page.
2. An active upCampo portal account, with the email (or login) and password you already use.
3. Query permissions granted by your company’s administrator. In the portal’s access control, they are the ones starting with “Consulta do tema” (topic query), and they apply per farm: you can grant crops on one farm and inventory on another. Where to check them is explained in the Users screen article.

If the login works and you still see “access not yet granted,” the third condition is what’s missing: the username and password are right, the permission is not there. Redoing the connection won’t fix it — ask your administrator.

Step by step in Claude

There are five steps, and the slowest one is typing your password.

1. Open Settings and go to Connectors.
2. Click Add and choose Add custom connector.
3. Enter the address https://mcp.upcampo.com.br/mcp and confirm.
4. The upCampo sign-in screen opens. Enter your email (or login) and password, and authorize access.
5. Start a new chat and ask about the farm.

The trap: leave the advanced OAuth fields blank

When you enter the address, Claude offers Advanced settings with two fields: “OAuth Client ID” and “OAuth Client Secret.” The temptation is natural — they look like username and password fields.

They are not. Leave them blank.

Filling them in with your portal login and password makes the connection fail before the sign-in screen even appears. It has happened to two users, and the symptom is misleading: it looks like a password problem, when it is the opposite — the password is right, just typed in the wrong place. Those fields are for people who run their own authentication server; the upCampo connector registers itself automatically. If the connection has already failed, remove the connector, add it again, and leave both fields empty.

Step by step in ChatGPT

In ChatGPT the feature appears as Plugins and requires a Business, Enterprise, or Edu plan, in the browser. That requirement comes from the assistant, not from upCampo.

1. In settings, open Plugins and turn on Developer mode (on Business plans, an administrator does this in the workspace settings).
2. Click Create and enter the address https://mcp.upcampo.com.br/mcp.
3. Choose OAuth as the authentication method and click Scan Tools.
4. Sign in with your upCampo account on the screen that opens and finish creating it.

One organizational detail: the plugin starts as a draft, visible only to its creator, and only the workspace administrator can publish it to the team. Agree on that beforehand, or the controller’s office will ask why only one person can use it.

The detailed walkthrough is on the connector page in the Help Center; the summary is on the connector page on our website.

How permissions and access logs work

This is what the client’s IT team asks first, and the answer is short: the connector creates no new access. It reuses, exactly as is, what your user already has in the portal.

• The assistant never holds your password. You type it on an upCampo screen; the assistant only receives an authorization, which you can revoke at any time from its connectors screen. Once revoked, access ends immediately.
• Farm by farm, topic by topic. If your user sees two of the group’s five farms, the assistant sees the same two. If you have inventory queries but not cost queries, the cost question goes unanswered — and it tells you which permission is missing instead of making something up.
• The connector does not store data. Each question triggers a live query and the answer goes to the assistant. What stays in the conversation from then on — history, dashboards, how long it is kept — follows the rules of Claude or ChatGPT and your account settings there.
• Every use is logged, just like portal access. It is the same access log the farm exports when it needs to audit who saw what. The general criteria are in the information security article.

In practice, enabling the connector for someone is not a new IT decision for the farm: it is the same decision as always — what this person is allowed to see — made on the same screen as always.

Where to start

Start with the question you ask someone else every week: how much it rained, how much is left to harvest, what’s left in inventory, which work orders are open. Connect, ask that question, and check the answer against the report once. Going the other way — asking for a big analysis on day one — tends to disappoint, because the answer depends on records that may not be complete yet. The AI sees exactly what the operation has recorded; it is the old farm management problem, now with someone who answers right away.

Frequently asked questions

What is an AI connector?

It is a bridge between an AI assistant and an external system. Registered once, it lets the assistant query the data at the source when you ask, instead of answering generically. The standard is MCP, which is open and adopted by Claude and ChatGPT.

What is the upCampo connector address?

https://mcp.upcampo.com.br/mcp. The same address works for Claude and ChatGPT.

Do I need an API key to connect?

No. Authentication uses OAuth: the sign-in screen belongs to upCampo and asks for the same credentials as the portal. There is no API key for end users.

In Claude’s advanced settings, what do I enter in “OAuth Client ID” and “OAuth Client Secret”?

Nothing — both fields stay blank. Filling them in with your portal login and password makes the connection fail before the sign-in screen even opens. You only type your password on the upCampo screen that opens next.

Can the connector change or delete data in my system?

Change, within limits: five entry types — rainfall, fueling, work order execution, work order, and invoice entry — always with your confirmation and only with the matching permission. Delete, no: no tool removes information.

What farm data can the assistant see?

Only data from the farms your user can already access in the portal, and only for the topics enabled for that user in access control. The connector does not expand permissions: it reuses the ones that exist.

I saw “access not yet granted” after signing in. What should I do?

The sign-in worked, but query permission is missing. Ask your company’s administrator to check, in the portal’s access control, the permissions starting with “Consulta do tema” (topic query). They are granted per farm.

Does it work on any Claude or ChatGPT plan?

In Claude, custom connectors are available on paid plans. In ChatGPT, the feature requires a Business, Enterprise, or Edu plan and works in the browser. In both cases, the requirement comes from the AI assistant, not from upCampo.