DropHaul Help
MCP server

DropHaul MCP server

Endpoint, authentication, and scope reference for the DropHaul MCP server.

DropHaul runs one Model Context Protocol server for the product itself.

This is the product MCP server, drophaul. It's a different server from the public, read-only docs MCP server, drophaul-docs, at https://docs.drophaul.app/mcp, which only serves this help site's content (search_docs, get_page, list_pages). Don't confuse the two when writing setup instructions.

Endpoint

https://majestic-emu-550.convex.site/mcp

That is the production Convex deployment (majestic-emu-550) HTTP action. Staging uses the same path on its own *.convex.site host; configure a staging URL directly in the client being tested.

The server speaks strict, stateless MCP 2026-07-28 over HTTP. Requests use POST; OPTIONS serves CORS; GET and DELETE explicitly return 405 because there is no session stream or termination operation. Every request carries its protocol version and client capabilities, every current DropHaul result is one JSON response, and server/discover replaces initialize.

Authentication

The server accepts either:

  • an OAuth 2.1 authorization-code + PKCE (S256) flow, discoverable at /.well-known/oauth-authorization-server, /.well-known/oauth-protected-resource, and /.well-known/oauth-protected-resource/mcp; or
  • a DropHaul personal access token as a bearer credential (see Personal access tokens).

DropHaul publishes Client ID Metadata Documents (CIMD) for public OAuth clients. Complete the client-managed OAuth flow shown by the client; no separate client registration step is required.

Scopes

Scopes are always intersected with the authenticated user's live DropHaul role permissions. A scope can narrow access but never widen it. See Security for the full scope list.

Per-client setup

See also Security and Troubleshooting.

On this page