Project44 MCP connector
The Project44 connector brings shipment tracking, loads, events and positions into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask where a shipment is and update it in plain language.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
181 tools
How to connect
How to connect Project44 to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Project44 once
-
Open Connections, choose Add connection, and pick Project44.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Project44 app credentials. Project44 authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Project44 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.
Project44 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 today. The plugin directory lives at chatgpt.com/plugins.
Project44 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.
Connect Project44 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.
Use cases
What teams do with Project44 through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Logistics
Find out where a shipment is right now
Ask for a shipment's latest position and event history in Project44 and get the answer without opening a tracking screen. Follow up with the next question in the same conversation.
-
Customer service
Answer a delivery question while the customer waits
Pull the current status and the last few events for the customer's shipment from Project44 and reply with a real update instead of a promise to check.
-
Operations
Start tracking a new load the moment it books
Create the shipment tracking and the load in Project44 from the booking details, so visibility starts on day one rather than after someone remembers to add it.
-
Supply chain
Count late shipments by lane or carrier
Search shipments in Project44 by status, carrier or destination and get counts back for the morning review, with filter suggestions when you are not sure how to narrow it.
-
Transportation
Correct load details after the carrier calls
Update a load's reference numbers or stops in Project44 right after the change comes in, without retyping it in the portal later.
-
Account management
Tag shipments with your own attributes
Add shipment attributes in Project44 such as customer, priority or region, so searches and counts match the way your team actually talks about freight.
Try asking
- “Where is shipment 4471 right now and when did it last move?”
- “How many shipments to Chicago are running late this week?”
- “Start tracking the new Maersk load and tag it priority.”
Compare
Elaichi vs Zapier MCP vs Composio for Project44
All three can connect Project44 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 Project44 tools | Allow or restrict single Project44 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 Project44 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 | $15 per user per month. | 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.
AI tools
Project44 tools for your AI agents
181 tools are ready to call through Elaichi's MCP endpoint the moment you connect Project44, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Project44 gets you
6 screens from the product, each doing one job for your Project44 account.
The agent
Ask where any shipment is, in plain words.
Answers come from live Project44 shipments, events and positions, not a stale report.
- shipments
- loads
- events
- positions
Ask Elaichi to work across your apps.
Where is shipment 4471 right now and when did it last move?
How many shipments to Chicago are running late this week?
Start tracking the new Maersk load and tag it priority.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Project44 to every client.
Claude, ChatGPT and Cursor reach Project44 through one governed endpoint, no SDK, no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
181 Project44 tools, with no code to write.
Shipments, loads, tracking history, events, positions and attributes, every method cataloged and ready.
- List all Project44 oauth 2 0 client applications
- Create a Project44 oauth 2 0 client application
- Get single Project44 oauth 2 0 client application by ID
- Update a Project44 oauth 2 0 client application by ID
ElaichiToolsToolboxes
Each team gets its own Project44 toolbox.
Logistics tracks shipments, customer service reads status, operations manages loads, each scoped to its team.
- Logistics
- Customer service
- Operations
- Supply chain
ElaichiToolboxesShared connections
Share one Project44 connection, never the credential.
One person connects Project44, teams work through it, and nobody else sees the credentials.
- Logistics NA
- Logistics EMEA
- Customer service
- Operations
ElaichiConnectionsAudit log
Every Project44 call names who made it.
When, who, what happened and which shipment or load, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the shipment digest itself.
Late shipments are fetched from Project44, grouped, drafted, approved by a person, then posted back.
Project44 digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch shipments
Project44
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 Michael Brennan
Approve Deny -
Post the digest
Project44
Queued
Collections and dashboards
Shipment health, computed without a model.
Four metrics, 14 days of shipments created and a split by team, refreshed on schedule.
Project44 health
Refreshed 4 minutes ago · every 15 minutes · from the shipments collection
Shipments
1,284 ↓ 12%
Loads
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Shipments created
Last 14 days
By team
Share of activity
Logistics NA 34%
Logistics EMEA 27%
Customer service 21%
Operations 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Project44 to Claude?
Connect Project44 in Elaichi by entering the app credentials Project44 gives you. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Project44 is ready to ask about.
Does Project44 work with ChatGPT and Cursor as well as Claude?
Yes. Once Project44 is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Project44 once and every client picks it up.
What can an AI agent actually do with my Project44 data?
With Project44 connected, an agent can look up a shipment's current position and event history, search shipments by carrier, destination or status, and count how many match. It can also start tracking a new shipment, create or update a load, and add your own attributes to shipments. Short, concrete asks such as "where is shipment 4471" work better than long paragraphs.
Does connecting Project44 give the AI everything in my account?
No. Every call to Project44 runs inside the access of the person who signed in to Elaichi, so the agent sees the shipments and loads that person can already see in Project44 and nothing more. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Project44?
Yes. Restrictions in Elaichi work per action, so you can allow reading Project44 shipment status while blocking deleting a tracking or changing a load. A restricted action is left out of the tool list the AI client receives, so it cannot be called no matter how the prompt is worded.
What happens to a Project44 connection when someone leaves?
Offboarding a person in Elaichi ends their access to Project44 through every client at once. A Project44 connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting Project44 once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Project44 MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Project44 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, 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 Project44?
Yes. Both let Claude, ChatGPT or Cursor use Project44. 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 Project44 call.
How is Elaichi different from Composio for Project44?
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 Project44: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Project44 in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.