Designing CLIs for Agents, Not Humans — Pedro Lopez, Airbyte
This post contributes to agent harness engineering by detailing the design and implementation of two distinct interfaces for AI agents to interact with company data via Airbyte's Context Store: a Multi-Cloud Platform (MCP) server and a Command Line Interface (CLI). For the MCP server, it highlights best practices such as limiting tool count with progressive discovery, using OAuth for authentication, supporting long-lived sessions, and the current limitations of URL elicitation. For the CLI, it emphasizes designing for agents rather than humans, advocating for JSON in/out, consistent noun-verb commands, shipping skills with the tool, and avoiding interactive prompts. The talk concludes by providing guidance on when to choose an MCP versus a CLI for agent integration.
More from the Agent Memory and Harness Engineering trail
- From Context to Memory: Your Agents Need a Real Memory Layer — Anders Swanson, Oracle
- Building on the Codex Harness — Dominik Kundel, OpenAI
- Stop Prompting — Greg Pstrucha, Sentry
- Brains vs Hands: How to Run AI Agents Safely in Production — Viren Baraiya
- We Mapped 115 Microservices for Our Coding Agents — Kamalakannan Nandagopal, Postman