New: ShipmentBot MCP Server

Connect your AI agents to your Amazon operations

ShipmentBot now speaks Model Context Protocol, giving ChatGPT and compatible agents a secure way to discover tools, request approval, and work with your ShipmentBot account context.

mcp.shipmentbot
POST https://app.shipmentbot.com/mcp

// Initialize protocol capabilities

{ "method": "initialize" }

// Discover available tools

{ "method": "tools/list" }

// Execute approved actions

{ "method": "tools/call" }

OAuth verified · tools.listChanged enabled

Built for agent-native commerce workflows

MCP gives AI clients a standard interface for discovering ShipmentBot capabilities while keeping your account protected behind explicit authorization.

Ask about operations

Let your AI assistant pull ShipmentBot context before answering replenishment, shipment, or account questions.

Trigger approved workflows

Expose safe tools that can prepare decisions, summarize next steps, or kick off repeatable operations.

Build agent-native automations

Use OpenAI Agents SDK or other MCP-compatible clients to wire ShipmentBot into your internal agent stack.

Simple connection flow

Add ShipmentBot as an MCP server in ChatGPT or any compatible client, complete OAuth, choose the right business/account, and start using approved tools from the chat.

MCP Server URL

https://app.shipmentbot.com/mcp
1

Discover

ChatGPT and compatible agents read ShipmentBot's MCP and OAuth metadata automatically.

2

Authorize

Your team approves access with OAuth 2.1, PKCE, scoped JWTs, and account-specific permissions.

3

Act

Agents call approved ShipmentBot tools over JSON-RPC, with live tool-change notifications over SSE.

Security by default

  • OAuth 2.1 with dynamic client registration and PKCE
  • RSA-signed JWT access tokens with refresh-token rotation support
  • Tokens scoped to the selected ShipmentBot business/account resource
  • Protected JSON-RPC endpoint and authenticated SSE notification stream

Give agents access without giving up control

Every MCP request is authenticated with a bearer token and resolved to the current ShipmentBot user and selected account. Tools run in a request-scoped context, so access decisions stay tied to the authorization your user approved.

The implementation supports JSON-RPC for tool calls and an authenticated SSE stream for tool-list changes and keepalive pings.

Ready to bring ShipmentBot into your AI workflow?

Connect through ChatGPT Integrations, OpenAI Agents SDK, or any MCP-compatible client using the ShipmentBot MCP server URL.