# MCP Tools in Claude Code

> How Claude Code adds tools from MCP servers. Why tool search keeps them from filling the context, and how a channel sends events in.

**Course:** [Claude Code Basics](https://learn.benibix.com/learn/ai-claude-code)  
**Time:** 10 min

**After this lesson you can:**

- Add an MCP server to Claude Code
- Explain what tool search saves
- Say what a channel adds to a session

## How Claude Code adds outside tools

An MCP server is a small program that gives Claude Code extra tools, such as one for your bug tracker or your database. You add one with claude mcp add and its name, or list them in a .mcp.json file the team shares. Each server can bring dozens of tools, and each tool has a long description.

Loading every one of those descriptions at the start would fill the context window before you typed a word. Tool search fixes that. Claude Code loads only each tool's name at first. When Claude needs a tool, the ToolSearch tool finds it by name or keyword and loads its full details then. ToolSearch never asks first.

Servers connect in the background as the session starts, so a slow one may not be ready yet. When Claude needs a tool from a server that is still on its way, it calls a tool that waits for it. Then it can use the server, and you do not have to start again.

MCP servers can also offer resources, which are things to read, such as files, records or pages. ListMcpResourcesTool lists them from every connected server. ReadMcpResourceTool reads one by its address. Neither asks first. The list leaves out MCP App pages, which are made for an app to show, not for Claude to read.

A channel is an MCP server that pushes events into a session that is already running. A chat message sent from your phone, or an alert from your CI, lands in the chat. Claude can act on it and reply the same way. You switch channels on when you start, with the --channels flag. They are still an early preview.

Channels need a sign-in with Anthropic, so they do not work through the big cloud firms such as Amazon Bedrock. Each channel keeps a list of who may send. Anyone on it can reach your session. So only add people you would trust at your keyboard.

```bash
claude mcp add --transport http tracker https://example.com/mcp
```
Add a remote MCP server named tracker. Its tools load by name, and in full only when Claude needs one.

![At the start, only a list of tool names sits in the context, such as create_issue, query_db and search. When query_db is chosen, its full details load. Tools that are never used never fill the context.](https://learn.benibix.com/diagrams/cc-mcp-tool-search.svg)

### Example: Jack connects 5 servers and keeps his room

Jack adds 5 MCP servers to his project, with 140 tools between them. His sessions still start with most of the context window free.

When he asks about a ticket, Claude looks up the tool it needs. It loads just that one and reads the ticket.

**Words in this lesson:** [MCP Server](https://learn.benibix.com/term/ai/mcp-server), [MCP Tool Search](https://learn.benibix.com/term/ai/mcp-tool-search), [ToolSearch Tool](https://learn.benibix.com/term/ai/tool-search-tool), [WaitForMcpServers Tool](https://learn.benibix.com/term/ai/wait-for-mcp-servers-tool), [MCP Resource Tools](https://learn.benibix.com/term/ai/mcp-resource-tools), [Claude Code Channel](https://learn.benibix.com/term/ai/claude-code-channel)

**Question:** What does tool search save?

**Answer:** Room in the context window, by loading full tool details only when needed. Without it, every tool's full description would load at the start. With it, only names load, and the full details of a tool load when Claude picks it.

---

Source: https://learn.benibix.com/learn/ai-claude-code/mcp-tools-in-claude-code
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-18
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
