Connect Claude to Rectangle, sign in with your work email, and start asking questions about your shipments and connected operational data.
Set up Claude with Rectangle
Connect Claude to the operational data your team manages in Rectangle. Ask about shipments, compare changes over time, and bring records from your connected systems into one conversation. The information available depends on what your organization has connected and enabled.
From the plugins directory
Open Rectangle’s listing in Claude’s directory and sign in with your work Claude account. Select Connect or Install, then follow the Rectangle sign-in prompts. If the listing is unavailable to your account, use the custom MCP option below or ask your Claude organization owner to enable access.
https://claude.ai/directory/2d14d385-6cf1-46a4-b026-28a993c1083d
You can also start from a conversation: open + → Connectors → Manage connectors → +, then search for Rectangle. Or browse Customize → Connectors. If your team distributes Rectangle as a plugin, look in Customize → Plugins → Discover and select Add.
Use the email your Rectangle administrator has approved. Enter the code sent to that email and approve the connection. Back in the conversation, enable Rectangle in the Connectors menu. On Team and Enterprise, an owner may need to make the connector available first.
Claude’s directory and connector guide
In Claude Code
Already connected Rectangle in Claude? Sign in to Claude Code with the same Claude account, then check the connection before adding it again. Connections from Claude can be available automatically when Claude Code uses your Claude subscription login.
Run /mcp inside Claude Code to check whether Rectangle is listed. If it is connected, start asking questions. If it is missing, restart Claude Code and confirm that you are signed in with the same Claude account.
For a direct connection, first ask your Rectangle administrator to enable Claude Code access. Then add the remote server from your terminal:
claude mcp add --transport http --scope user rectangle https://prod.mcp.rectanglehq.com/functions/v1/shipment-mcp
Start Claude Code, run /mcp, choose Rectangle, and complete the browser sign-in. If your team requires a preconfigured OAuth client, use the client ID and callback port they provide; Claude Code also supports prompting securely for a client secret.
Claude Code’s MCP setup and authentication reference
Configuring a custom MCP connection
Use a custom connector when your team gives you a Rectangle MCP URL, or when Rectangle is not available in your directory. Your work email must already have access to your organization in Rectangle.
Open Customize → Connectors → + Add → Add custom connector. On Team or Enterprise, an owner first adds it in Organization settings → Connectors → Add → Custom → Web.
Name the connector Rectangle and enter this remote MCP server URL:
https://prod.mcp.rectanglehq.com/functions/v1/shipment-mcpContinue to the authentication settings and choose Sign in now. If your administrator supplied an OAuth client ID and secret, select Use your own OAuth client and enter them there.
Finish adding the connector. On the Rectangle sign-in page, enter your approved work email, type the code from your email, and approve the connection.
Return to Claude. In the conversation’s + → Connectors menu, enable Rectangle and try a shipment question.
If Rectangle says access has not been assigned, ask your administrator to assign that email to your organization. If Claude cannot complete authorization, ask them to check the approved OAuth client and callback settings.
Claude’s custom connector instructions
A closer look
Start with a shipment you recognize. Use the shipment number, load number, or customer reference you already work with, and include a date or customer name if the reference could match several records. Ask Claude to cite the relevant source and separate confirmed facts from missing information.
I’ll check the matching shipment and its available history, then separate recorded changes from anything that is still unknown.
Questions you can ask
Use these examples as starting points, then adapt the dates, customers, and references to your work. The shipment connection supports shipment searches and available change history. The wider use cases below need the corresponding order, inventory, or supplier data enabled by your team. Example replies illustrate the approach; they are not live results.
Freight and logistics
Find loads that need attention, compare carrier performance, or prepare a customer update. Give Claude a time window and ask it to explain which records support the answer.
Explore: Find the best carrier for a load · Understand customer margins
I’ll review the available shipment records and highlight exceptions, with the supporting shipment reference and timestamp.
Procurement
When purchasing records are connected, bring requests, open orders, and supplier commitments together. Ask Claude to flag missing information before drafting a purchasing brief or follow-up.
Explore: Turn a parts request into a purchase-ready brief · Get supplier commitments before an order slips
With purchasing data connected, I can organize the outstanding commitments and draft a follow-up for your review.
Warehousing and distribution
With inventory and order data available, investigate shortages across locations and see which customer orders are affected. Ask for feasible options and their tradeoffs before deciding on a transfer or a new purchase.
Explore: Recover backorders from stock in your network · Consolidate inbound purchase orders
With inventory and order records connected, I can compare available stock with demand and outline possible recovery options.
Manufacturing and CPG
Connect material availability and inbound deliveries to production needs or a promotion. Focus on the items that could miss the required date, and ask Claude to distinguish confirmed commitments from estimates.
Explore: Find the missing material before the production slot · Check inventory before a promotion
With production requirements and inbound records connected, I can trace each risk to its source and identify the next detail to verify.



