How y-vex/chronodrive-mcp works
Chronodrive MCP exposes product search and cart management to MCP-compatible assistants. The assistant can use search results to help build a reviewed grocery cart from a meal plan; recipe interpretation and review happen outside this repository. The server dispatches tool calls to the Chronodrive client, which manages authentication, search, and cart API requests. The README documents these capabilities; the graph follows the sampled server and client source, without implying unsampled integrations.
Main entry points: server.py Tool dispatcher · client.py Authentication
Components 12
MCP interface
- Tool server
server.py - Tool dispatcher
server.py
Chronodrive client
- API client
client.py - Authentication
client.py - Product search
client.py - Cart operations
client.py
Local state
- Session file
client.py - Frontend config cache
client.py
Other components
- MCP assistant
- Chronodrive APIs
- Chronodrive Connect
- Chronodrive website
Connections 14
- MCP assistant → Tool server: invokes tools
- Tool server → Tool dispatcher: dispatches calls
- Tool dispatcher → Authentication: authenticates
- Tool dispatcher → API client: gets session
- Tool dispatcher → Product search: searches products
- Tool dispatcher → Cart operations: manages cart
- API client → Authentication: validates session
- Authentication → Session file: reads/writes
- API client → Frontend config cache: loads config
- Authentication → Chronodrive Connect: requests tokens
- Authentication → Chronodrive APIs: fetches customer/cart
- Product search → Chronodrive APIs: searches products
- Cart operations → Chronodrive APIs: reads/writes cart
- API client → Chronodrive website: fetches API config