> ## Documentation Index
> Fetch the complete documentation index at: https://handler.alduncanson.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Documentation MCP

> Use Handler's hosted documentation MCP server so agents can discover Handler commands and structured CLI workflows.

# Give agents current Handler docs

Handler's documentation is available through a hosted MCP server at:

```text theme={null}
https://handler.alduncanson.com/mcp
```

Connect an agent to this MCP endpoint when you want it to use Handler reliably
instead of guessing command names or output shapes from model memory.

## When this is useful

* an AI coding assistant needs to call A2A agents from a shell
* an internal agent should generate `handler --output json ...` commands
* a workflow needs up-to-date examples for sessions, tasks, and server configuration
* you want agents to discover Handler docs through MCP rather than a web browser

## Recommended agent instruction

Give the agent a short, operational instruction like this:

```text theme={null}
Use Handler to send A2A protocol messages, inspect agent cards, and manage A2A
tasks. Prefer structured output with `handler --output json` or
`handler --output ndjson` when another program or agent will consume the result.
```

## Agent-friendly CLI pattern

For single responses, prefer JSON:

```bash theme={null}
handler --output json message send \
  --server production-agent \
  --text "Summarize the current task state"
```

For streaming responses, prefer newline-delimited JSON:

```bash theme={null}
handler --output ndjson message stream \
  --server production-agent \
  --text "Run the long workflow and stream progress"
```

## Discover commands programmatically

Handler also exposes its own CLI shape for agents and automation:

```bash theme={null}
handler --output json schema
```

```bash theme={null}
handler --output json describe message send
```

```bash theme={null}
handler --output json describe task get
```

Use these commands when an agent needs to construct invocations dynamically.
They are also useful for validating wrapper tools, command palettes, and
generated documentation.

## Built-in local agent behavior

The bundled local agent uses the same hosted docs MCP endpoint by default:

```bash theme={null}
handler server run agent
```