How to integrate Shipengine MCP with Google ADK

This guide walks you through connecting Shipengine to Google ADK using the Composio tool router. By the end, you'll have a working Shipengine agent that can generate shipping label for new order, track status of outgoing packages, validate customer address before shipping through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Shipengine account through Composio's Shipengine MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Shipengine logoShipengine
Api Key

ShipEngine is a shipping API that connects with multiple carriers to manage shipments, labels, and tracking. Streamline your shipping process and reduce manual effort with one unified tool.

66 Tools

Introduction

This guide walks you through connecting Shipengine to Google ADK using the Composio tool router. By the end, you'll have a working Shipengine agent that can generate shipping label for new order, track status of outgoing packages, validate customer address before shipping through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Shipengine account through Composio's Shipengine MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Shipengine with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLILangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get a Shipengine account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Shipengine
  • Build an agent that connects to Shipengine through MCP
  • Interact with Shipengine using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

What is the Shipengine MCP server, and what's possible with it?

The Shipengine MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Shipengine account. It provides structured and secure access to your shipping operations, so your agent can perform actions like generating shipping labels, tracking packages, validating addresses, and managing carrier integrations on your behalf.

  • Automated label creation and management: Instantly generate, purchase, and void shipping labels across multiple carriers, letting your agent streamline fulfillment without manual entry.
  • Real-time package tracking: Ask your agent to track shipments by carrier or tracking number to get up-to-date delivery statuses and shipment histories.
  • Address validation and correction: Have your agent validate and standardize shipment addresses to prevent delivery errors and reduce returns.
  • Carrier rate comparison: Enable your agent to fetch and compare real-time shipping rates from all connected carriers, helping you save on delivery costs.
  • Shipping manifest and batch processing: Let your agent generate manifests or process batches of shipments in a single command, making high-volume shipping fast and efficient.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Shipengine via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["shipengine"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Shipengine operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Shipengine and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["shipengine"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Shipengine operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Shipengine with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Shipengine using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Shipengine tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

TOOLS

Supported Tools

Every Shipengine action and event your agent gets out of the box.

Add Tag to Shipment

Tool to add a tag to a shipment for organization and filtering.

Add to Batch

Tool to add shipments or rate IDs to an existing batch.

Cancel Shipment

Tool to cancel a shipment by ID.

Connect LTL Carrier

Tool to connect an LTL carrier account to ShipEngine.

Connect Shipsurance Account

Tool to connect a Shipsurance insurance account to ShipEngine.

Create Account Image

Tool to create a new account image in ShipEngine.

Create Package Type

Tool to create a custom package type definition in ShipEngine.

Create Tag

Tool to create a new tag in ShipEngine.

Create Tag 2

Tool to create a new tag for organizing shipments.

Create Warehouse

Tool to create a new warehouse.

Create Webhook

Tool to create a ShipEngine webhook.

Delete Account Image by ID

Tool to delete a ShipEngine account image by its ID.

Delete Batch

Tool to delete a batch by ID.

Delete Package

Tool to delete a custom package type by ID.

Delete Warehouse

Tool to delete a warehouse from your ShipEngine account.

Delete Webhook

Tool to delete a ShipEngine webhook subscription.

Disconnect Carrier

Tool to disconnect a carrier account from ShipEngine.

Disconnect Shipsurance

Tool to disconnect a Shipsurance insurance account from ShipEngine.

Download File

Tool to download a file from ShipEngine.

Get Account Image by ID

Tool to retrieve account image settings by label image ID.

Get Batch by External ID

Tool to retrieve batch details using an external batch ID.

Get Batch by ID

Tool to retrieve detailed information about a specific batch by its ID.

Get Batch Errors

Tool to retrieve errors that occurred during batch processing.

Get Bulk Rates

Tool to get shipping rates for multiple shipments in a single request.

Get Insurance Balance

Tool to retrieve the current Shipsurance insurance funds balance.

Get LTL Carrier Credential Requirements

Tool to retrieve credential requirements for connecting an LTL carrier.

Get LTL Carrier Features

Tool to retrieve features supported by an LTL carrier.

Get LTL Carrier Options

Tool to list available options/accessorials for an LTL carrier.

Get LTL Carrier Packages

Tool to list available package/handling unit types for an LTL (Less Than Truckload) carrier.

Get LTL Carrier Services

Tool to list available services for an LTL carrier.

Get Package by ID

Tool to get details of a specific custom package type by ID.

Get Shipment by External ID

Tool to retrieve shipment details using an external shipment ID.

Get Shipment by ID

Tool to retrieve a shipment by ID.

Get Shipment Rates

Tool to retrieve shipping rates for an existing shipment.

Get Tracking Information

Tool to retrieve tracking information for a shipment.

Get Warehouse by ID

Tool to retrieve details of a specific warehouse by ID.

Get Webhook by ID

Tool to retrieve details of a specific webhook by ID.

List Account Images

Tool to list all account images.

List Account Settings

Tool to list all account settings for the ShipEngine account.

List Batches (v2)

Tool to list all batches with comprehensive filtering options.

List Carrier Package Types

Tool to list all available package types for a specific carrier.

List Labels (Extended)

Tool to list all shipping labels with comprehensive filtering options.

List LTL Carriers

Tool to list all LTL (Less-Than-Truckload) carrier accounts connected to your ShipEngine account.

List Manifests (Advanced)

Tool to list all manifests with optional filtering by warehouse and carrier.

List Packages

Tool to list all package types.

List Scheduled Pickups

Tool to list all scheduled pickups with optional filters.

List Shipments (v2)

Tool to list all shipments with optional filtering parameters.

List Tags (v2)

Tool to list all tags in your account.

List Warehouses

Tool to list all warehouses.

List Webhook Events

Retrieve a list of available webhook event types supported by ShipEngine.

List Webhooks

Tool to list all webhooks configured on your account.

Parse Address

Tool to parse unstructured address text and extract structured address components.

Process Batch Labels

Tool to process a batch to create and purchase shipping labels for all shipments in the batch.

Remove From Batch

Tool to remove shipments or rate IDs from a batch.

Remove Tag from Shipment

Tool to remove a tag from a shipment.

Start Tracking Package

Tool to subscribe to tracking updates for a package via webhooks.

Stop Tracking Package

Tool to unsubscribe from tracking updates for a package.

Track LTL Shipment

Tool to track an LTL shipment using carrier code and PRO number.

Update Account Image By ID

Tool to update an account image by ID in ShipEngine.

Update LTL Connection

Tool to update LTL carrier connection credentials in ShipEngine.

Update Package Type

Tool to update an existing custom package type definition.

Update Shipment

Tool to update an existing shipment's details.

Update Shipments Tags

Tool to update tags on one or more shipments in bulk.

Update Warehouse

Tool to update an existing warehouse's details and address.

Update Webhook

Tool to update a ShipEngine webhook.

Validate Address

Tool to validate and normalize shipping addresses.

FRAMEWORKS

How to build Shipengine MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Shipengine MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Shipengine MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Shipengine MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Shipengine MCP with Claude Cowork

Codex logo

Codex

Use Shipengine MCP with Codex

OpenClaw logo

OpenClaw

Use Shipengine MCP with OpenClaw

Hermes logo

Hermes

Use Shipengine MCP with Hermes

CLI logo

CLI

Use Shipengine MCP with CLI

LangChain logo

LangChain

Use Shipengine MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Shipengine MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Shipengine MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Shipengine MCP with LlamaIndex

CrewAI logo

CrewAI

Use Shipengine MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Shipengine MCP server, the agents and LLMs can only access a fixed set of Shipengine tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Shipengine and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Google ADK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Shipengine tools.

Yes, absolutely. You can configure which Shipengine scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Shipengine data and credentials are handled as safely as possible.

Start with Shipengine.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Shipengine tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies