MCP server · ShipMonk

shipmonk-api

ShipMonk serves a live MCP endpoint from its own developer-docs host. tools/list responds anonymously over streamable HTTP (SSE) with five spec-driven tools. These are ReadMe's documentation-MCP tools rather than one tool per ShipMonk operation: four are introspection tools over ShipMonk's OpenAPI description and the fifth, execute-request, is a generic HAR-shaped proxy that can call any operation in the spec. So the agent-facing surface is complete (every REST operation is reachable) but indirect (no per-operation tool names or typed inputs).

Open endpoint → ShipMonk provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: ShipMonk Type: Hosted endpoint Transport: http Host: apidocs.shipmonk.com

Endpoint

https://apidocs.shipmonk.com/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "shipmonk": { "url": "https://apidocs.shipmonk.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "shipmonk": { "command": "npx", "args": ["-y", "mcp-remote", "https://apidocs.shipmonk.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://apidocs.shipmonk.com/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

list-endpoints — Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into get-endpoint.
get-endpoint — Gets detailed information about a specific API endpoint, including security schemes and servers.
search-endpoints — Performs a deep search through paths, operations and parameters to discover relevant API endpoints.
execute-request — Executes an API request with a given HAR request object.
get-server-variables — Gets the server variables for each server within a specific OpenAPI spec.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.