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

# MCP

> Connect to Model Context Protocol servers for dynamic tool discovery

## Overview

MCP (Model Context Protocol) Server Tools connect your agents to external MCP servers, automatically discovering all available tools. Instead of configuring each tool manually, point to an MCP server URL and all its tools become available instantly.

## Why Use MCP Tools?

**Dynamic Discovery**: Tools are discovered automatically when agents run—no manual configuration needed. One MCP server can provide dozens of tools.

**Community Ecosystem**: Connect to popular services like Tavily Search, GitHub, Slack, Google Drive, PostgreSQL, and more through standardized MCP servers.

## Creating an MCP Server Tool

### 1. Start Creation

* Click **Tools** in the sidebar → **New Tool** → Select **MCP Server**

### 2. Configure

**Tool Name**: Descriptive name like "Tavily Search" or "GitHub Tools"

**Description**: What the server provides and when to use it

**Server URL**: The MCP server endpoint

```
https://mcp.tavily.com
```

**API Key** (Optional): Enter if the server requires authentication

<Note>
  Use HTTPS (`https://`) or WSS (`wss://`) in production. HTTP/WS only for local
  development.
</Note>

### 3. Verify Server

Click **Verify Server**. The system connects to the server and shows discovered tools. Verification is required before saving.

### 4. Create Tool

Click **Create Tool**. You'll be redirected to the Tools page.

## Using MCP Tools

Assign the MCP tool to your agent in the agent's Tools section. When the agent runs, it automatically discovers and uses all tools from the server.

**Example**: Connect Tavily MCP server → Agent gains `web_search`, `news_search`, and `research_query` tools automatically.

## Best Practices

**Descriptive Names**: Use clear names like "Tavily Web Search", not "MCP Server 1"

**Verify Before Saving**: Required step ensures the server is accessible and working

**Use HTTPS in Production**: Only use HTTP for local development

## Troubleshooting

**Connection Failed**: Verify URL, check network/firewall, ensure correct protocol

**No Tools Discovered**: Confirm server implements MCP correctly, check server health

**Tool Errors**: Verify agent parameters match tool schema, check server logs

## Finding MCP Servers

Browse official servers at [github.com/modelcontextprotocol/servers](https://github.com/modelcontextprotocol/servers) or search GitHub for "mcp-server".

## Next Steps

<CardGroup cols={2}>
  <Card title="Assign Tools to Agents" icon="link" href="/guides/agents/managing-tools">
    Configure agent tool access
  </Card>

  <Card title="Test Your Agents" icon="flask" href="/guides/agents/testing-agents">
    Test agents before production
  </Card>
</CardGroup>