Laverie MCP server
Laverie publishes an MCP (Model Context Protocol) endpoint for authorized, read-only access to laundry service catalog information.
Connection details
- Server URL
https://laverie.me/mcp- Transport
- Streamable HTTP
- Discovery card
- MCP server card
- API catalog
- API catalog
Available capabilities
The advertised scope is read-only catalog access: laundry services, prices, and service locations/zones. Discover the exact tool names and argument schemas with tools/list; do not assume the names or parameters.
Authentication
The MCP endpoint requires authorization. Clients should use an access token obtained through the server's supported OAuth flow, then send Authorization: Bearer <access_token> on requests. See OAuth protected resource metadata and OAuth authorization server metadata for discovery. Do not put tokens in URLs or browser-visible pages.
Connect a client
- Configure a Streamable HTTP MCP connection to
https://laverie.me/mcp. - Complete the OAuth flow supported by the client and server.
- Send MCP
initialize, followed bynotifications/initialized. - Call
tools/listand inspect the returned schemas before invoking tools.
Example MCP client configuration
In an MCP client supporting Streamable HTTP, add a remote server with the following settings:
{
"name": "laverie-catalog",
"url": "https://laverie.me/mcp",
"transport": "streamable-http"
}This is an illustrative connection profile; the exact configuration format depends on your MCP client. Complete the supported OAuth flow to authorize access. After connecting, use tools/list to discover laverie_services, laverie_prices, and laverie_locations and their current input schemas.
For protocol-level testing, send an authenticated initialize request, follow it with notifications/initialized, then call tools/list. Internal test scripts are not publicly hosted.