How to Connect Make to the Easyship MCP Server

This article explains how to set up the Easyship MCP server in Make so your automation scenarios can manage shipping workflows with zero API setup and optional AI-powered automation.

Before You Begin

You'll need:

  • An active Make account
  • Access to your Easyship Dashboard
  • An Easyship account (API access is available on all plans at no extra cost)

Step 1: Get Your Easyship API Token

  1. Go to your Easyship Dashboard and click Connect
  2. Click New Integration
  3. Scroll down to API Integration
  4. Under Integration Type, select I am developing a custom integration
  5. Name the key Easyship MCP for easy reference
  6. Keep the default version 2024-09 and click Connect
  7. On the next page, click Access Token and copy it using the copy button

Required scopes: Your API token must include the following scopes. Missing scopes will cause some tools to fail while others continue to work.

public.shipment:read              public.shipment:write
public.label:write                public.pickup:read
public.pickup:write               public.address_validation:write
public.address_validation_domestic:write
public.shipment_document:read     public.transaction_record:read
public.analytics:read             public.rate:read
public.track:read

You can check and update scopes at any time in Dashboard → Connect → API without creating a new token.

Step 2: Add the Easyship MCP Server to Make

  1. Log into Make and click Create a new scenario
  2. Select any trigger (e.g. Shopify, webhook, form submission)
  3. Click + Add module → search for and select MCP Client
  4. Choose your execution type (see Step 3), then click Add+ New MCP Server
  5. Enter the following:
    • Server URLhttps://mcp.easyship.com/mcp
    • API Access Token → Paste your Easyship API token from Step 1

Note: Make automatically sends your token as Bearer <token> — paste only the token value, not the word "Bearer".

Security: Never share your API token in a chat window or commit it to version control. If you accidentally expose it, revoke and rotate your key immediately in the Easyship Dashboard under Connect → API.

Step 3: Choose Your Execution Type

Make's MCP Client offers two execution modes:

Option A — Run a Tool

Select a specific Easyship tool and map inputs from previous modules. Best for structured, deterministic workflows where you know exactly which action to run.

Option B — Execute an Action with AI

Select specific tools or All tools, then describe the task in the Task field. Best for dynamic, multi-step workflows. Example prompt:

Create a shipment using order data from previous step, choose the cheapest courier,

generate a label, and return tracking details.

Easyship currently supports 24 actions, with more coming soon. See the full list of available actions.

Step 4: Try It Out

Test your scenario with a prompt like:

I want to ship a parcel from New York, USA to Toronto, Canada. Origin: 350 5th Avenue, New York, US 10001. Destination: 220 Yonge Street, Toronto, ON, Canada M5B 2H1. Parcel: 1.98 lb, 6 × 4 × 2 cm. Item: Business documents, quantity 1, HS Code 4911.99, declared value $1.00 USD, category documents, DDU. Show me the cheapest and best value shipping options with delivery times and courier names.

For a full list of available tools and workflows, see the [Easyship MCP Developer Docs].

Example Workflows

1. Shopify Order → Smart Shipping Automation

Tools: Shopify + Easyship MCP + Make

  1. Trigger: New Shopify order
  2. MCP Client (AI execution): fetch rates → select best courier → create shipment → generate label
  3. Send tracking details to customer

Outcome: Fully automated fulfillment, AI-driven courier selection, faster order processing.

2. Zendesk Ticket → Automatic Tracking Response

Tools: Zendesk + Easyship MCP

  1. Trigger: New support ticket
  2. MCP Client (AI prompt): "Find shipment using order ID and return tracking status with link."
  3. Send reply automatically

Outcome: Instant WISMO resolution, reduced support workload.

3. Post-Purchase Customer Communication

Tools: Easyship MCP + Make + email/SMS tools (e.g. Klaviyo, WhatsApp)

  1. Trigger: Shipment created
  2. MCP Client → Fetch tracking info
  3. Send automated messages: shipping confirmation, delivery updates, delivery confirmation

Outcome: Proactive communication, better customer experience, fewer support tickets.

Best Practices

  • Choose your execution type based on complexity: use AI execution for multi-step automation, Run a Tool for precision tasks
  • Write clear AI prompts that specify the goal and expected output
  • Store tracking data centrally in your CRM or database
  • Add error handling routes for failed actions
  • Always validate addresses before creating shipments

FAQs

Do I need to include "Bearer" when pasting my token? 

No. Make automatically prepends Bearer to the token. Paste only the token value in the API Access Token field.

What if the MCP Client module can't connect? 

Double-check the server URL (https://mcp.easyship.com/mcp) and your API token. Delete the connection and re-add it if the issue persists.

Why is my API token not working? 

Check the scopes in the Easyship Dashboard under Connect → API. Enable all the scopes listed in Step 1 for full access.

Do I need to pay for the API token? 

No. Easyship provides API access across all plans at no extra cost. If you exceed the included API limits for your plan, overage fees may apply. See pricing plans and included limits.

Can I use the same token across multiple tools? 

Yes. The same API token works across any MCP client. Be mindful of rate limits and avoid running conflicting operations simultaneously.

Need Further Assistance?

If you're experiencing an error that isn't covered above, submit a bug report. Include the tool name, error code, and request ID from the error response - these help us diagnose the issue faster.

Was this article helpful?
0 out of 0 found this helpful
Popular Topics