What MCP is
MCP (Model Context Protocol) is how AI clients call CurbWaste. The partner endpoint is Streamable HTTP athttps://api.curbwaste.com/mcp. Tools use the same company API keys and scopes as the partner REST API and invoke the same services underneath — not a separate data plane.
Use REST when your application calls CurbWaste directly. Use MCP when an MCP-compatible agent should discover and invoke those capabilities as tools.
Tools
A tool is available when your API key includes its scope.mcp:tools:* covers every mcp:tools:… scope, including mcp:tools:connect, which is required to open a session. Resource scopes (customers:read, catalog:write, and so on) unlock the matching REST-style tools.
Where a name exists both as a resource tool and as an mcp:tools: tool, the server exposes the mcp:tools: tool.
Customers
Catalog and pricing
Locations and zones
Orders
Billing
Dispatch
Exact REST contracts for the same resources are in the API Reference.
Auth and scopes
Create keys and choose scopes in the Developer Platform under API Keys. Clients authenticate with:401 / 403, and scope meaning. Prefer the minimum scopes the agent needs.
Connect an AI client
- Open the Developer Platform
- Create an API key under API Keys with the scopes your agent needs
- Open MCP and copy the configuration for your AI client
- Keep the
cw_live_…key in a secure secret store
Safety
Successful writes through MCP use the same services as REST, so they can emit the same webhooks (for examplecustomer.created / location.updated).
Authenticated MCP tool calls share your company’s partner API rate limit with REST /v1.
Related
Usage
Company rate limits shared by REST and MCP.
Authentication
Company API keys, Bearer auth, and scopes shared with REST.
Customers
Account hub agents work with via customer tools.
API Reference
REST contracts for the resources MCP tools call.