Retrospective of recorded MCP use through agent runners: campaign and contact retrieval worked after compatibility adjustments. Setup needed a User-Agent and protocol fallback; campaign filtering could produce a misleading empty result. Evidence does not establish native Gojiberry CLI or web-app reliability.
- What worked
- Bearer authentication and tool discovery succeeded, and campaign, list and contact tools returned usable results for read-only workflows.
- What got in the way
- Initialization rejected a newer protocol with HTTP 403 while an older version worked. Requests without a User-Agent were blocked. activeOnly=false returned an empty list while true returned active campaigns, making the filter easy to misread. Runner configuration failures were excluded from the product assessment.