Cropwise MCP Server

Overview

The Cropwise MCP Server connects AI assistants such as ChatGPT, Claude, and Cursor to Cropwise through the Model Context Protocol (MCP). Ask questions in natural language about your farms, fields, agricultural operations, scouting, and satellite imagery, then explore the results through follow-up questions.

Your assistant discovers the available capabilities automatically. Access depends on your Cropwise permissions and your workspace's service contracts and entitlements.

Connection details

Setting	Value
Production MCP URL	`https://api.base.cropwise.com/mcp`
Transport	Streamable HTTP
Authentication	Bearer access token (client credentials) or interactive OAuth with Cropwise sign-in

For server-to-server integrations, obtain an access token using your client ID and client secret, then send it directly in the Authorization: Bearer <access_token> header. No browser sign-in is required. See the Cropwise Authentication Guide for the supported grants and token request details.

For interactive use, add the server URL to your assistant and sign in when prompted. MCP clients that support OAuth handle authentication discovery automatically.

Before you connect

You need:

Cropwise client credentials for server-to-server access, or a Cropwise account for interactive sign-in, with access to the data and services you want to use.
An assistant or MCP client that supports remote Streamable HTTP connections and either custom authorization headers or interactive OAuth.
Permission to add custom MCP connections in your assistant's account or workspace.

If you need client credentials or your assistant is not yet approved for interactive OAuth, contact the Cropwise team.

Connect your AI client

Choose the authentication method your integration needs. Client credentials are recommended for most Open Platform integrations, including server-to-server API calls. Custom MCP connection availability and menu labels can vary by plan, version, and workspace policy. Your administrator may need to enable or add the connection first.

Client credentials: connect with a bearer token

The examples below assume you already have a valid access token. To obtain one, follow Method 1: Client Credentials Grant in the authentication guide. Pass only the access token to the MCP server, not your client ID or client secret. No browser sign-in is required.

Cursor (bearer token)

Add the following to your user-level ~/.cursor/mcp.json, or merge the entry into its existing mcpServers object:

{
  "mcpServers": {
    "cropwise": {
      "url": "https://api.base.cropwise.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ACCESS_TOKEN"
      }
    }
  }
}

Replace YOUR_ACCESS_TOKEN with your existing access token, then enable the server in Cursor's MCP settings. This configuration sends the token directly without browser sign-in. Keep the configuration private and out of version control; use your client's environment-variable or secret-management support where available. Update the token when it expires.

Claude Code (bearer token)

Store your existing access token securely in the CROPWISE_ACCESS_TOKEN environment variable, then add the server with an explicit authorization header:

claude mcp add --transport http Cropwise https://api.base.cropwise.com/mcp \
  --header "Authorization: Bearer ${CROPWISE_ACCESS_TOKEN}"

Run /mcp inside Claude Code to check the connection. You do not need to follow a browser authentication prompt when supplying a valid token. The shell expands the environment variable when you run this command; it does not automatically renew the saved token. Update the configured header when you obtain a new token, and keep the client configuration private.

Other clients (bearer token)

Add a remote server named Cropwise with the URL https://api.base.cropwise.com/mcp.
Choose Streamable HTTP if a transport is requested.
Configure a custom HTTP header named Authorization with the value Bearer YOUR_ACCESS_TOKEN, replacing the placeholder with your token. If the client has a bearer-token field instead, enter only the token unless its instructions say otherwise.
Connect without starting an interactive OAuth flow. Your client must send the authorization header on every MCP HTTP request.
Request a new access token and update the header when the token expires. Automated integrations should manage token renewal securely.

If your assistant does not support custom headers or bearer-token authentication, use a client that does, or use the interactive OAuth option below.

Use this option when you want to sign in as a Cropwise user through your assistant. The Authorization Code Grant documentation explains the interactive flow; OAuth-capable MCP clients handle the browser prompts and token exchange for you.

ChatGPT

Open ChatGPT's custom MCP server setup, following the ChatGPT connection guide.
Add a custom MCP server named Cropwise with the URL https://api.base.cropwise.com/mcp.
Choose OAuth authentication and create the connection.
Follow the prompt to sign in to Cropwise and review the requested access.
Start a conversation and select the Cropwise connection so ChatGPT can use it.

Claude

Open Customize > Connectors in Claude and choose Add custom connector.
Enter Cropwise as the name and https://api.base.cropwise.com/mcp as the remote MCP server URL.
Follow the setup prompts, then connect and sign in to Cropwise when requested.
In a conversation, open the + menu, choose Connectors, and enable Cropwise.

For managed workspaces, an owner may need to add the connector before members can connect. See Claude's custom connector guide for the current steps for your plan.

Cursor (interactive OAuth)

Add the following to your user-level ~/.cursor/mcp.json, or merge the entry into its existing mcpServers object:

{
  "mcpServers": {
    "cropwise": {
      "url": "https://api.base.cropwise.com/mcp"
    }
  }
}

Open Cursor's MCP settings, enable the server, and complete authentication when prompted. Sign in to Cropwise in the browser and review the requested access.

Claude Code (interactive OAuth)

Add the remote server:

claude mcp add --transport http Cropwise https://api.base.cropwise.com/mcp

Run /mcp inside Claude Code, select the Cropwise server, and follow the authentication prompt to sign in and authorize access.

Other clients (interactive OAuth)

In your client's MCP or connector settings:

Add a remote server named Cropwise.
Set its URL to https://api.base.cropwise.com/mcp and choose Streamable HTTP if a transport is requested.
Choose OAuth authentication if requested.
Complete Cropwise sign-in and authorization in the browser.
Enable the connection in your conversation.

Verify the connection

Start with a small request:

Show my Cropwise account and the workspaces I can access.

If you have access to multiple workspaces, name the one you want to explore in your next question.

Available capabilities

Use your assistant to explore:

Farms and fields: find farms, compare field areas, and summarize your workspace's agricultural footprint.
Agricultural operations: review planned and completed work and the products applied.
Scouting and field conditions: summarize observations, rainfall, notes, crop growth stages, and scouting analytics.
Disease risk: explore available forecasts and distinguish expected risks from conditions already observed in the field.
Satellite imagery: inspect vegetation trends, compare NDVI over time, and generate NDVI zones from available imagery.
Crops and inputs: find crops, varieties, and catalog information for agricultural inputs.

Available capabilities depend on your service access and may evolve over time. Your assistant discovers what is available when it connects. Interactive visualizations also depend on the assistant's support for MCP Apps.

Example questions

Name the workspace or farm when you have access to more than one, and specify the date range when it matters.

Farm and field overview

List the farms in my workspace, with field counts and total area in hectares.

Which is the largest field on Santa Rosa farm? Show its calculated and declared area.

Operations and scouting

What spraying operations were recorded on Santa Rosa farm last month, and which products were applied?

When was each field on Santa Rosa farm last scouted?

Summarize the notes mentioning rust on Santa Rosa farm during September 2026.

Analytics and satellite imagery

Which fields on Santa Rosa farm need attention according to the latest scouting analytics? Include the indicator and observation window.

Show the NDVI time series for Field 12 on Santa Rosa farm from 1 July to 31 August 2026.

Generate three NDVI zones from the latest available image for Field 12 on Santa Rosa farm.

Follow up naturally, for example: "Compare those fields" or "Limit that summary to last month." Results depend on recorded data and your service access.

Permissions, privacy, and safe use

Permissions still apply. The server does not grant extra access to another workspace, organization, or farm. Requests use the identity and permissions associated with the supplied access token: the application for client credentials, or the signed-in user for interactive OAuth. Resource-authorization behavior is specific to each service.
Licensing still applies. Contract- and entitlement-gated tools are not offered to callers who do not meet their access requirements. Connecting an AI client does not purchase or activate a service.
Data reaches your AI client. Tool results are returned to the client you connect. Your client and model-provider configuration determine what is sent to an AI provider and how it is retained. Review your organization's privacy and security requirements before connecting.
Keep credentials and downloads private. Do not share client secrets, passwords, access tokens, or sensitive download links in prompts or public channels, or commit them to version control. Store secrets securely and remove configured tokens or disconnect the assistant when you no longer need the connection.
Review AI answers and actions. Check dates, units, and scope before using an answer for an operational decision, and review tool-approval requests before proceeding. Distinguish forecasts from recorded observations and missing values from zero.

Troubleshooting

Symptom	What to check
No option to add a custom MCP connection	Check your assistant's plan and workspace policy, or ask your administrator to enable it.
A bearer-token connection returns `401 Unauthorized`	Check that every MCP HTTP request includes `Authorization: Bearer <access_token>`, not your client ID or secret. If the token has expired, obtain a new one using the Client Credentials Grant and update the configured header.
The client opens a browser when you intended to use a bearer token	Check that your client supports custom headers and that its authorization header is configured. Use the bearer-token examples above rather than the interactive OAuth setup.
Interactive OAuth is rejected or shows `unapproved_client`	Confirm the server URL and contact the Cropwise team to check approval for your assistant.
Interactive sign-in fails or the connection has expired	Disconnect and reconnect, then sign in to the correct Cropwise account when prompted.
An access error or an expected capability is missing	Check the token's permissions and scopes, and the workspace's active service contracts and entitlements. Obtain a new token or reconnect after access changes.
A query returns no data	Confirm the workspace, farm, field, and date range. Check whether records exist and the identity associated with your token can read them.
An answer is incomplete or a response is too large	Ask about a smaller set of fields or a shorter period, and request the remaining results as a follow-up.
An interactive chart does not render	Check whether your assistant supports MCP Apps. Ask for a text summary instead.

For help, contact the Cropwise team with the client name and version, tool name, timestamp, and error message. Do not include access tokens, client secrets, or sensitive farm data.