MCP Server
Connect any MCP-compatible AI agent or tool to the Homerunner API using the Model Context Protocol over HTTP. The server exposes your shipments, tracking, products, and returns as callable tools.
Endpoint
The MCP server speaks the Streamable HTTP transport (JSON mode). Point your client at the POST endpoint:
POST https://mcp.homerunner.com
enableJsonResponse: true).
Authentication
There are two ways to authenticate, depending on whether your client can open a browser. Both use your Homerunner email address and integration token (from Settings → Integrations) — the same credentials you use for the REST API.
Programmatic clients (no browser)
If you connect the server from code — Anthropic's Messages API MCP connector, OpenAI's Responses API, or any custom client — there is no OAuth flow to complete. Send your credentials directly as the bearer token: the base64 of email:integration-token.
Authorization: Bearer <base64("email:integration-token")>
This is the value you pass as the connector's authorization token (e.g. authorization_token on the Anthropic connector, or the MCP tool's Authorization header on OpenAI). It is exactly the email:integration-token pair, base64-encoded — the same shape as REST Basic auth, but sent as a Bearer token rather than Basic. There is no username/password exchange and no token endpoint to call: the server validates the credentials and resolves your workspace on each request. SSO-only tools work too, provided the workspace has MCP access enabled.
Interactive clients (browser)
Desktop and CLI clients that can open a browser — Claude Desktop, Claude Code, MCP Inspector — use the standard OAuth flow automatically when you supply the server URL. It follows OAuth 2.1 (which consolidates RFC 6749 / 6750 and makes PKCE mandatory) with dynamic client registration (RFC 7591):
- 1Client discovers endpoints from /.well-known/oauth-authorization-server.
- 2Client registers itself at /register (dynamic client registration).
- 3Client opens the authorization URL at /authorize — a form asks for your email and integration token.
- 4After you submit, the client is redirected back with an authorization code and exchanges it for an access token at /token.
- 5The client sends the access token as a Bearer token on all MCP requests.
Quick start — Claude Desktop
Add the following to your claude_desktop_config.json:
{
"mcpServers": {
"homerunner": {
"type": "http",
"url": "https://mcp.homerunner.com"
}
}
}
Claude will prompt you to authenticate the first time.
Available tools
Required parameters are highlighted. Tools marked SSO require signing in with your Homerunner account (the OAuth flow handles this automatically).
create_shipment.confirm_cancel_shipment to execute.awaiting_confirmation: true. Call confirm_redact_shipment to proceed — this cannot be undone.redact_shipment.create_shipment.carrier_key values are the valid service_codes to pass into create_shipment.insurance when creating a shipment.delete_shipping_method to remove methods before updating.get_checkout to find method IDs first.awaiting_confirmation: true. Call confirm_delete_checkout to proceed.delete_checkout.create_ticket.store_ticket_file first for file attachments.create_ticket.get_shipment_ticket.{ filename, base64_file } — they are uploaded automatically (images, PDF, DOCX, XLSX, CSV, TXT; max 10 MB each, up to 10).conversation_id and the file as { filename, base64_file }; it is uploaded and posted as a short message (images, PDF, DOCX, XLSX, CSV, TXT; max 10 MB).Updated 25 July 2026 at 10:50