# 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. Source: https://elaichi.ai/connectors/project44/ ## Facts | | | | --- | --- | | Application | Project44 | | Category | Logistics | | AI tools | 181 | | Authentication | App credentials | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Project44 is connected - 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. ## Connect Project44 in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Project44. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Project44 tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Project44 MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Project44 to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a Project44 tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Project44 through Elaichi ### Find out where a shipment is right now Logistics. 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. ### Answer a delivery question while the customer waits Customer service. 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. ### Start tracking a new load the moment it books Operations. 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. ### Count late shipments by lane or carrier Supply chain. 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. ### Correct load details after the carrier calls Transportation. Update a load's reference numbers or stops in Project44 right after the change comes in, without retyping it in the portal later. ### Tag shipments with your own attributes Account management. Add shipment attributes in Project44 such as customer, priority or region, so searches and counts match the way your team actually talks about freight. ## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## 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 my team share one Project44 connection? Yes. One person connects Project44 in Elaichi and shares the connection with a team, and nobody else ever handles the Project44 credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every shipment lookup or load update. ### 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. ## All 181 Project44 tools Every tool below is callable through https://api.elaichi.ai/mcp once Project44 is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Project44 oauth 2 0 client applications** (List). List the OAuth 2.0 client applications of your project44 account. Returns: id, name. - **Create a Project44 oauth 2 0 client application** (Create). Register an OAuth 2.0 client application in project44. Returns: id, name, secret. - **Get single Project44 oauth 2 0 client application by ID** (Get). Get an OAuth 2.0 client application in project44 by client id. Returns: id, name. Required: id. - **Update a Project44 oauth 2 0 client application by ID** (Update). Update an OAuth 2.0 client application in project44 by client id. Returns: id, name. Required: id. - **Delete a Project44 oauth 2 0 client application by ID** (Delete). Delete an OAuth 2.0 client application in project44 by client id. Returns an empty 204 response on success. Required: id. - **Create a Project44 oauth 2 0 client application secret** (Create). Generate a new client secret for a project44 client application; the former secret stops working. Returns: id, name, secret. Required: client_id. - **Create a Project44 oauth 2 0 token generation** (Create). Grant a project44 access token for a client id and secret (client credentials grant). Returns: access_token, expires_in, token_type. - **Create a Project44 shipment tracking** (Create). Start tracking a shipment in project44, or append data to an existing tracked shipment. Returns: id, attributes, accessGroups, createdDateTime, costs, contents, and 8 more fields. - **Project44 shipment tracking bulk update** (Update). Start tracking a shipment in project44, or replace the data of an existing tracked shipment. Returns: id, attributes, accessGroups, createdDateTime, costs, contents, and 8 more fields. - **Get single Project44 shipment tracking by ID** (Get). Get a tracked shipment in project44 by shipment id, with its stops and route segments. Returns: id, attributes, accessGroups, createdDateTime, identifiers, lastModifiedDateTime, plan, routeInfo, and 2 more fields. Required: id. - **Delete a Project44 shipment tracking by ID** (Delete). Delete a shipment route in project44 by shipment id to stop tracking the shipment. Returns no documented response body (HTTP 202). Required: id. - **Get single Project44 shipment tracking history by ID** (Get). Get the full tracking history of a project44 shipment by shipment id. Returns: costs, contents, events, exceptions, positions, shipment, states, sharingContext, and 1 more field. Required: id. - **Get single Project44 shipment event history by ID** (Get). Get the event history of a project44 shipment by shipment id. Returns: costs, contents, events, exceptions, shipment, states, sharingContext, sensorContext. Required: id. - **Get single Project44 shipment position history by ID** (Get). Get the position history of a project44 shipment by shipment id. Returns: positions, shipment. Required: id. - **List all Project44 shipment tenant attributes** (List). List the tenant attributes of a project44 shipment. Returns: attributeName, attributeValues. Required: shipment_id. - **List all Project44 shipment attributes** (List). List all shipment attribute definitions in project44. Returns: name. - **Create a Project44 shipment attribute** (Create). Create a predefined shipment attribute in project44; needs an organization admin. Returns: infoMessages, shipmentAttributeDefinition. - **Project44 shipment search search** (Search). Search project44 shipments that match a set of criteria. Returns: allShipmentIdentifiers, activeVehicleIdentifier, allActiveVehicleIdentifiers, activeSegmentMode, allSegmentModes, accessGroupIds, and 21 more fields. - **Project44 shipment counts search** (Search). Count the project44 shipments that match a set of criteria. Returns: total. - **Project44 filter suggestions search** (Search). Get suggested values for shipment search criteria in project44. Returns a list of string values. - **Create a Project44 shipment load** (Create). Create a load in project44. Returns: id. - **Get single Project44 shipment load by ID** (Get). Get a load in project44 by load id. Returns: id, createdDateTime, deletedDateTime, deliveryStopReference, description, handlingUnits, identifiers, involvedParties, and 3 more fields. Required: id. - **Update a Project44 shipment load by ID** (Update). Update a load in project44. Returns no documented response body (HTTP 202). Required: id. - **Delete a Project44 shipment load by ID** (Delete). Delete a load in project44. Returns no documented response body (HTTP 202). Required: id. - **List all Project44 shipment loads** (List). List the loads of a project44 master shipment. Returns: id, createdDateTime, deletedDateTime, deliveryStopReference, description, handlingUnits, identifiers, involvedParties, and 3 more fields. Required: master_shipment_id. - **Create a Project44 inventory item** (Create). Create an inventory item in project44. Returns: id. - **Get single Project44 inventory item by ID** (Get). Get an inventory item in project44 by project44 id. Returns: id, consumeByDateTime, description, externalID, inventoryDimensionalWeight, inventoryIdentifiers, and 14 more fields. Required: id. - **Update a Project44 inventory item by ID** (Update). Update an inventory item in project44. Returns: id. Required: id. - **Delete a Project44 inventory item by ID** (Delete). Delete an inventory item in project44. Returns no documented response body (HTTP 202). Required: id. - **Project44 inventory items bulk create** (Create). Create several inventory items in project44 in one call. Returns: ids. - **List all Project44 inventory items** (List). Search inventory items in project44. Returns: id, consumeByDateTime, description, externalID, inventoryDimensionalWeight, inventoryIdentifiers, and 14 more fields. - **Create a Project44 inventory order** (Create). Create an order in project44. Returns: id. - **Get single Project44 inventory order by ID** (Get). Get an order in project44 by project44 id. Returns: id, additionalOrderIdentifiers, attributes, billToLocation, createdDate, deletedDateTime, and 20 more fields. Required: id. - **Update a Project44 inventory order by ID** (Update). Update an order in project44. Returns: id. Required: id. - **Delete a Project44 inventory order by ID** (Delete). Delete an order in project44. Returns no documented response body (HTTP 202). Required: id. - **List all Project44 inventory orders** (List). Search orders in project44. Returns: id, additionalOrderIdentifiers, attributes, billToLocation, createdDate, deletedDateTime, and 20 more fields. - **List all Project44 inventory order related orders** (List). List the orders related to a project44 order. Returns: id, additionalOrderIdentifiers, attributes, billToLocation, createdDate, deletedDateTime, and 20 more fields. Required: order_id. - **Project44 ltl rate quotes search** (Search). Query LTL rate quotes in project44. Returns: id, alternateRateQuotes, capacityProviderAccountGroup, capacityProviderQuoteNumber, carrierCode, contractId, and 15 more fields. - **Project44 ltl transit time quotes search** (Search). Query LTL transit time quotes in project44. Returns: capacityProviderAccountGroup, carrierCode, deliveryDateTime, errorMessages, infoMessages, transitDays. - **Create a Project44 ltl dispatch** (Create). Create (dispatch) an LTL shipment in project44. Returns: id, capacityProviderBolUrl, infoMessages, packingVisualizationUrl, pickupDateTime, pickupNote, shipmentIdentifiers. - **Project44 ltl dispatch cancel** (Cancel). Cancel a dispatched LTL shipment in project44 by shipment id. Returns: infoMessages, shipmentIdentifiers. Required: shipment_id. - **Create a Project44 ltl dispatch cancellation** (Create). Cancel a dispatched LTL shipment in project44 by shipment identifier. Returns: infoMessages, shipmentIdentifiers. - **List all Project44 ltl pro numbers** (List). List the ProNumber blocks in project44. Returns: blockEnd, blockStart, currentProNumber, remainingProsInBlock, vendorId. - **Create a Project44 ltl pro number** (Create). Generate a ProNumber for a vendor in project44. Returns: proNumber, vendorId. - **Project44 ltl pro numbers bulk update** (Update). Update a ProNumber for a vendor in project44. Returns a string value. - **Project44 ltl image retrieval search** (Search). Query LTL shipment document images in project44. Returns: documentType, imageFormat, imageUrl, infoMessages, proNumber. - **Create a Project44 ltl electronic bol** (Create). Create an LTL electronic bill of lading (BOL) in project44. Returns: images, messageStatus, referenceNumbers, transactionDate, version. - **Update a Project44 ltl electronic bol by ID** (Update). Update an LTL electronic BOL in project44 (pass the ProNumber as id). Returns: images, messageStatus, referenceNumbers, transactionDate, version. Required: id. - **Delete a Project44 ltl electronic bol by ID** (Delete). Delete an LTL electronic BOL in project44 (pass the ProNumber as id). Returns no documented response fields (HTTP 200). Required: id. - **List all Project44 ltl address book** (List). List the locations in the project44 LTL address book. Returns: address, contact. - ...and 131 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.