# Use TeamBoost task context in Claude Code

Illustrative planning brief; no automatic product import.

Illustrative case: Claude Code needs current blocked work for a review summary, but no task creation was requested.

## Decision

Configure the approved remote endpoint and auth mode, then request only the needed task-context tools.

## Owned work

- Establish connection mode
  - Owner role: Operator
  - Acceptance evidence: The approved TeamBoost MCP endpoint and Streamable HTTP transport are confirmed.
- Verify workspace binding
  - Owner role: Operator
  - Acceptance evidence: The chosen auth mode resolves the intended organization.
- Bound the agent request
  - Owner role: User
  - Acceptance evidence: The request names the read-only review purpose and excludes product writes.

## Workflow

1. Use current Claude Code MCP configuration guidance.
2. Confirm TeamBoost auth mode and workspace evidence without pasting secrets into a work brief.
3. Inspect tool results for scope and completeness before summarizing.

## Judgment

TeamBoost source write-scope enforcement remains pending. Client-side allowed-tool choices help express intent but are not proof of a server-enforced boundary.


## Filled illustrative decision

The illustrative agent brief requests a summary of blocked work in one approved workspace. The operator verifies the remote endpoint and organization binding, then permits only the needed context reads. The summary names unresolved inputs; it does not create tasks or claim that the client connection was tested here.


## Scope conditions

- Transport / Approved Streamable HTTP endpoint / Confirm provider configuration
- Workspace / Auth-mode-specific organization binding / Stop on ambiguity or access failure
- Operation / User requested a bounded context read / Do not invoke write tools merely because they are listed


## Workflow questions

### Does connecting authorize task creation?

No. Connection and a user-approved operation are separate decisions.

### Do CLI preview flags apply to MCP?

No. TeamBoost MCP tool calls have a different contract; do not assume --dry-run or --apply behavior.

## Product connection

The source-backed TeamBoost agent workflow starts Claude Code with a scoped task read and explicit limits on subsequent actions.

Confirm account availability before adopting this manual outline.