Agworld MCP connector
The Agworld connector brings fields, activities, product applications, seeding records and reported problems into Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client, with each person signed in as themselves and every call logged.
- OAuth or API key
- Free 14-day trial
- No credit card
Which fields had a seeding activity recorded this week?
Working in Agworld with Elaichi
-
List all Agworld active ingredient amounts
-
List all Agworld activity asset IDS
-
Get single Agworld activity asset by ID
How to connect Agworld to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Agworld MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Agworld MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Agworld MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Agworld MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Agworld MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Agworld to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Agworld through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Agworld is logged.
-
Agronomy
Check what went on a field
Before a visit, ask for every product application on a field this season, with the active ingredient amounts, and read it back in one place.
-
Operations
See which operations ran this week
Pull the activity operations, the operators who did them and the assets they used, so the week's work is clear without opening each record.
-
Compliance
Answer a spray record question fast
When an auditor asks what was applied where and by whom, look up the product applications and compound products for that field and date range.
-
Finance
Reconcile inputs against recorded applications
List the compound products and application activities for a block of fields to compare against supplier invoices.
-
Management
Summarize seeding progress across properties
Ask how many fields have a seeding activity recorded this month and which ones do not, then share the summary with growers.
-
Grower services
Review problems reported in the field
Bring up the activity problems logged across a client's fields so an agronomist can plan the next visit around them.
Try asking
- “Which fields had a seeding activity recorded this week?”
- “List product applications on the north block since March.”
- “Show problems reported across all fields this month.”
What connecting Agworld gets you
6 screens from Elaichi, each doing one job for your Agworld account.
Ask Elaichi to work across your apps.
Which fields had a seeding activity recorded this week?
List product applications on the north block since March.
Show problems reported across all fields this month.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your Agworld fields in plain words.
Get answers from live Agworld activities and applications without opening a single record.
Copy the endpoint
AI apps
Agworld from any MCP client, one endpoint.
Claude, ChatGPT and Cursor reach Agworld through one governed endpoint, no SDK, no shared API key.
Tool catalog
155 Agworld tools, ready with no code.
Fields, activities, product applications, seedings, problems and more, covered without writing a line.
Toolboxes
Every team gets its own Agworld toolbox.
Agronomy, operations and compliance each work from a toolbox scoped to their job.
Shared connections
Share Agworld access without sharing a credential.
One person connects Agworld, teammates work through it and never see the key.
Audit log
Every Agworld call names who ran it.
When, who, what happened and which field or activity, in one append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Agworld digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch fields
Agworld
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Agworld
Queued
Workflows
A schedule starts Agworld work, a person approves.
Agworld activities are fetched, grouped and drafted into a digest, then approved and posted back.
Agworld health
Refreshed 4 minutes ago · every 15 minutes · from the fields collection
Fields
1,284 ↓ 12%
Activities
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Fields created
Last 14 days
By team
Share of activity
Agronomy North 34%
Agronomy South 27%
Operations 21%
Compliance 18%
Collections and dashboards
Agworld numbers computed on a schedule, no model.
Four metrics, fourteen days of activities created, and a breakdown by team, refreshed automatically.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Agworld
All three can connect Agworld to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Agworld tools | Allow or restrict single Agworld tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Agworld call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Agworld tools for your AI agents
155 tools are ready to call through Elaichi's MCP endpoint the moment you connect Agworld, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Agworld to Claude?
Connect Agworld in Elaichi first, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Agworld's own sign-in uses an OAuth application you register inside Agworld yourself, so somebody brings a client ID and secret once, or an API key if your organization prefers that. Nothing further has to be generated on the Claude side, and nobody else on the team handles that step again.
Does Agworld work with ChatGPT and Cursor as well as Claude?
Yes. Agworld is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Each person signs in as themselves whichever client they use.
What can an AI agent actually do with my Agworld data?
With Agworld connected, an agent can look up fields, activities, operations, seeding records, product applications, compound products, active ingredient amounts, operators, assets and reported problems, and answer questions about them. It can tell you what was applied on a field, which operations ran last week, or where problems were logged. Short, concrete asks such as a field name and a date range work better than long sentences.
Does connecting Agworld give the AI access to every farm and field?
No. Agworld access follows the person who signed in, so an agent only sees the properties, fields and activities that person can already see in Agworld. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Agworld?
The Agworld connector only reads records, so an agent cannot delete or change fields, activities or applications through it. Restrictions still apply per action, on a role or on one person, if you want to limit what can be looked up. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Agworld connection when someone leaves?
Offboarding that person in Elaichi ends their Agworld access at once, in every client they used. A shared Agworld connection keeps working for everyone else on the team. Disconnecting Agworld once in Elaichi removes it from every client.
Does the Agworld MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Agworld is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Agworld?
Yes. Both let Claude, ChatGPT or Cursor use Agworld. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Agworld call.
How is Elaichi different from Composio for Agworld?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Agworld: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Agworld in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot