# Choose CLI or MCP for a TeamBoost agent workflow

Illustrative planning brief; no automatic product import.

Illustrative case: one agent can run a native CLI locally, while another needs a remote tool interface for task context.

## Decision

Choose the interface that fits the runtime and operation; do not copy flags or auth assumptions across them.

## Owned work

- Check runtime access
  - Owner role: Designer
  - Acceptance evidence: The agent can either resolve the native executable or reach an approved MCP endpoint.
- Compare the operation contract
  - Owner role: Reviewer
  - Acceptance evidence: CLI preview/apply behavior is not assigned to MCP write calls.
- Verify context and result
  - Owner role: Operator
  - Acceptance evidence: The chosen interface uses intended workspace evidence and checks its outcome semantics.

## Workflow

1. Identify whether the agent executes local commands or remote tools.
2. Compare supported reads/writes and authentication requirements.
3. Test a bounded read before expanding the workflow.

## Judgment

Neither interface guarantees a successful live workflow merely because code or documentation exists.


## Illustrative interface choice

Native CLI: executable on the agent runtime PATH, browser-authenticated context and previewed writes.
Remote MCP: approved HTTP endpoint, auth-mode-specific workspace binding and named tool calls.
Shared requirement: bounded user intent and evidence-based results.


## Before / after

Before: Treat every agent connector as the same API with identical flags and permission behavior.

After: Choose the transport and operation contract explicitly, then verify context and outcomes for that interface.


## Workflow questions

### Is the CLI skill an MCP server?

No. It guides native command use; TeamBoost’s MCP server is a separate Streamable HTTP interface.

### Can I reuse CLI --apply with an MCP tool?

No. Each interface has its own write contract and result evidence.

## Product connection

Choose between the source-backed TeamBoost CLI and MCP workflows using their actual authentication, context and write behavior.

Confirm account availability before adopting this manual outline.