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

# Protocols & Transports

> How Rogue communicates with your AI agents

## Overview

Rogue can communicate with your agent using various protocols and transports, providing flexibility in how you integrate your agent for evaluation. This allows you to build your agent using any framework of your choice and connect it to Rogue through standardized communication protocols.

## Supported Protocols

Rogue currently supports two main protocols for agent communication:

<CardGroup cols={2}>
  <Card title="A2A Protocol" icon="comments" href="/rogue/protocols/a2a">
    Google's Agent-to-Agent protocol with HTTP transport
  </Card>

  <Card title="MCP Protocol" icon="plug" href="/rogue/protocols/mcp">
    Model Context Protocol with SSE and STREAMABLE\_HTTP transports
  </Card>
</CardGroup>

## How It Works

When you configure Rogue to evaluate your agent, you'll specify:

1. **Protocol**: A2A or MCP
2. **Transport**: The communication transport method (varies by protocol)
3. **Endpoint**: Your agent's URL
4. **Authentication**: Optional security credentials

Rogue's `EvaluatorAgent` will then communicate with your agent using the selected protocol to conduct test scenarios and evaluate performance.

## Configuration

Regardless of which protocol you choose, configuring Rogue to connect to your agent is straightforward:

### In the Web UI

1. Navigate to the configuration page
2. Enter your agent's endpoint URL
3. Select your protocol and transport
4. Configure authentication if needed
5. Save and proceed to evaluation

### In the CLI

```bash theme={null}
uvx rogue-ai cli \
  --evaluated-agent-url http://your-agent:8080 \
  --protocol a2a \
  --transport http
```

### In the TUI

The TUI will guide you through the configuration process interactively.