ShipBob API MCP Server

Created By
mattcoatswortha year ago
Overview

what is ShipBob API MCP Server?

ShipBob API MCP Server is a comprehensive Model Context Protocol (MCP) server designed for interacting with ShipBob's e-commerce fulfillment API, enabling users to manage their e-commerce operations efficiently.

how to use ShipBob API MCP Server?

To use the ShipBob API MCP Server, clone the repository, install the necessary dependencies, create a .env file with your ShipBob API key, and start the server using Node.js.

key features of ShipBob API MCP Server?

  • Manage product catalogs, orders, and inventory levels.
  • Handle shipments and fulfillment processes.
  • Configure webhooks for real-time notifications.
  • Process return requests and manage fulfillment center locations.
  • Generate and retrieve various reports related to inventory and orders.

use cases of ShipBob API MCP Server?

  1. Automating order management for e-commerce businesses.
  2. Tracking inventory levels across multiple fulfillment centers.
  3. Integrating with sales channels to streamline operations.
  4. Generating reports for better decision-making in e-commerce.

FAQ from ShipBob API MCP Server?

  • What are the prerequisites to use the server?

You need Node.js 16 or higher and a ShipBob API key.

  • How do I test the server?

You can test the server using the MCP Inspector, which provides a web interface for browsing tools and testing inputs.

  • Is there documentation available for the ShipBob API?

Yes, you can access documentation for various sections of the ShipBob API through the provided resources.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

43 minutes ago