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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago