---
title: "What MCP Is"
description: "The connective tissue — and why one connection becomes five workflows."
order: 20
duration: "10 min"
chapter: "05-trusting-your-own-data"
type: lesson
---

## The connective tissue

MCP — the Model Context Protocol — is a standard that lets any process expose **tools** (actions Claude can call), **resources** (data Claude can read), and **prompts** (templates Claude can use) to any Claude surface. Think of it as a USB-C port for AI integrations — one standard connector, everything plugs in.

An MCP server is just a process. It can run locally on your machine or on a remote host. Two transport modes handle the connection:

| Transport | How It Works | When to Use |
|-----------|-------------|-------------|
| **stdio** | Claude spawns the server as a child process, communicates over stdin/stdout | Local tools, CLI wrappers, filesystem access |
| **HTTP** | Server runs remotely, Claude connects over streamable HTTP | Cloud services, shared team servers, SaaS integrations |

The protocol is JSON-RPC over whichever transport you choose. The server advertises what it can do, and Claude calls it when the user's intent matches. No special SDK, no vendor lock-in — just a process that speaks the protocol.

## Connect once, verify everywhere

This is the key insight of the entire course. When you connect an MCP server to Claude, it does not just work in one place. It works across *every* Claude surface:

<div class="callout">
  <div class="callout-label">One MCP Server, Every Surface</div>
  <p><strong>Chat and Projects:</strong> Connectors answer questions in any conversation, on any device</p>
  <p><strong>Terminal:</strong> Claude Code calls your MCP tools directly while coding</p>
  <p><strong>Phone:</strong> Remote Control gives your phone access to the same MCP servers running locally</p>
  <p><strong>Dispatch:</strong> Sessions spawned on your desktop from your phone inherit all connected MCP servers</p>
  <p><strong>Channels:</strong> Event-driven triggers — Telegram, Discord, webhooks — can call any MCP tool in response</p>
  <p><strong>Routines:</strong> Recurring cloud jobs use MCP to query databases, deploy code, check metrics</p>
</div>

Before MCP, you would build a Slack integration, then a CLI tool, then a web dashboard, then a mobile app — four implementations of the same capability. With MCP, you build the server once. Claude is the universal client. Every new surface Anthropic ships automatically gets access to every MCP server you have already connected.

For Cornwall Market, the implication is concrete: connect QuickBooks once via MCP, and that connection works when Sarah is at her desk in Claude Code, on her phone via Remote Control, through a Monday morning routine, and through a channel alert when a sync fails. One integration, five access methods.

This is why MCP is the *multiplier*. Every tool you connect does not add capabilities linearly — it multiplies across every access method.

## What production servers actually look like

These are not toy demos. These are MCP servers in daily production use, and they illustrate the range of what the protocol can do.

### Neon — Database

Neon's MCP server gives Claude direct access to your Postgres database:

| Tool | What It Does |
|------|-------------|
| `run_sql` | Execute any SQL query and return results |
| `get_database_tables` | List all tables with their schemas |
| `create_branch` | Branch the database for safe migration testing |

The `create_branch` tool is the standout. Neon's branching means Claude can test a migration on a copy of your production database, verify it works, and only then apply it to the real thing.

### Chrome DevTools — Browser

The Chrome DevTools MCP server gives Claude programmatic control of a real browser — faster and more reliable than Computer Use for browser tasks:

| Tool | What It Does |
|------|-------------|
| `navigate` | Open any URL in Chrome |
| `screenshot` | Capture the current page state |
| `lighthouse_audit` | Run a full Lighthouse performance audit |
| `click` / `fill` | Interact with page elements by selector |

### TezLab — Real-World IoT

TezLab connects Claude to real vehicle data: charge history, drive logs, battery health, efficiency metrics. A good example of MCP reaching beyond software into physical systems.

### QuickBooks — The Obvious First Integration

For Cornwall Market — and for many companies — the most impactful first MCP integration is the accounting system. QuickBooks via MCP gives Claude access to customers, vendors, invoices, bills, and transactions.

This is where the first transition meets the second. You have made your chart of accounts and categorization rules legible (skills from Chapter 04). Now you connect the actual financial data (MCP). Claude can answer "which vendors have outstanding invoices over 30 days?" without you pulling a report. And because it is MCP, that answer is verifiable — the tool call shows exactly which QuickBooks query produced the data.

## Check your understanding

Answer in your own words — write it down before opening the key. Your tutor grades against the criteria and generates fresh variants on retries.

**Q1.** Explain why MCP is a multiplier rather than an adder. Use a concrete example: one new connection, and what it becomes across access methods.

<details>
<summary>Answer key — attempt every question first</summary>

## Answer key

### Q1

**Model answer:** A capability plugged in via MCP is available through every access method at once — terminal, phone, cloud sessions, event triggers, schedules. Connect QuickBooks once and you did not add one feature: you added a desk query, a phone query, a Monday routine, and a sync-failure alert handler. Capabilities × access methods, not capabilities + 1.

**Pass criteria:** states the every-surface property; example shows one connection appearing as several workflows; multiplication framing present

</details>


**Next:** [Your MCP Roadmap](/mastering-claude/05-trusting-your-own-data/21-your-mcp-roadmap/)