Trackkr MCP Server
# Trackkr MCP Server — Smart Lockerless Parcel Management
A Model Context Protocol server that enables AI agents to autonomously manage incoming packages, log parcels, cross-reference unit directories, and track pick-up signatures without physical locker hardware.
- **Website:** [https://trackkr.app](https://trackkr.app)
- **Glama MCP Endpoint:** [https://glama.ai/endpoints/xuvltpe45j/mcp](https://glama.ai/endpoints/xuvltpe45j/mcp)
- **Direct MCP Endpoint:** [https://trackkr.app/mcp](https://trackkr.app/mcp)
- **Repository:** [https://github.com/DTLA-Professional-Services-LLC/trackkr-mcp](https://github.com/DTLA-Professional-Services-LLC/trackkr-mcp)
- **License:** MIT
---
## Capabilities / Tools List
- **`get_pending_parcels`**: Fetches the current ledger of uncollected packages, highlights aging stats (5+ days), and returns structured JSON context.
- **`log_incoming_parcel`**: Accepts parsed text from Google Cloud Vision OCR label scans and/or external `photoUrl` links (automatically downloaded and hosted on Firebase Storage), cross-references internal Firestore unit listings, and schedules automated email alerts via SendGrid and US (`+1`) SMS alerts via the Quo Phone API.
- **`release_parcel_with_signature`**: Updates parcel state to `Picked Up`, records the timestamp, and securely saves the digital signature PNG layout to Firebase Storage.
---
## Configuration & Environment Variables
| Variable | Required | Description |
|----------|----------|-------------|
| `FIREBASE_CONFIG_JSON` | **Yes** | Path to your authorized Firebase service account credentials (or stringified JSON). |
| `USE_MOCK_OCR` | No | Set to `true` during local staging to bypass paid Google Cloud Vision API billing counters. |
---
## Quickstart Guide
### Run via `npx`
```bash
FIREBASE_CONFIG_JSON="./service-account.json" \
USE_MOCK_OCR="true" \
npx -y github:DTLA-Professional-Services-LLC/trackkr-mcp
```
### Add to `claude_desktop_config.json`
```json
{
"mcpServers": {
"trackkr-mcp": {
"command": "npx",
"args": ["-y", "github:DTLA-Professional-Services-LLC/trackkr-mcp"],
"env": {
"FIREBASE_CONFIG_JSON": "/path/to/service-account.json",
"USE_MOCK_OCR": "true"
}
}
}
}
```
TDQS
Scored across 3 tools
Each tool targets a distinct parcel lifecycle stage: viewing pending parcels, logging incoming parcels, and releasing parcels with signature. There is no meaningful overlap in purpose or resource, so an agent can easily select the right tool.
All tool names use snake_case with a leading verb and a parcel-related noun (get_pending_parcels, log_incoming_parcel, release_parcel_with_signature). The pattern is predictable, and the third tool's modifier does not disrupt readability.
Three tools is lean but reasonable for a focused intake-to-release workflow. It is slightly under-scoped for a parcel-tracking domain that likely benefits from additional query and update operations.
The core lifecycle is covered: log incoming, list pending, and release with signature. However, there are notable gaps such as getting a parcel by ID, listing full history/all parcels, updating parcel details, canceling/deleting, and managing notifications or units.