Module 1 · Lesson 3
Servers vs Tools
MCP Servers are long-running processes that expose multiple tools. Understand the difference — and explore six real server types.
MCP Servers vs Direct Tool Calls
An MCP Server is NOT the same as a single tool. A server is a persistent process that can expose many tools, maintain state across calls, and manage connections. Here's how they compare:
MCP Servers
Direct Tool Calls
LifecycleLong-running process. Starts once, handles many requests.
LifecycleOne-off execution. Each call is independent.
CapabilitiesExposes multiple tools, resources, and prompts through a single server.
CapabilitiesSingle function with defined inputs and outputs.
StateMaintains state across calls. Database connections stay open. Context persists.
StateStateless. Each invocation starts fresh with no memory of previous calls.
DiscoveryClients discover available tools automatically via the MCP protocol.
DiscoveryTools must be explicitly defined and configured per integration.
TransportCommunicates over stdio (local) or Streamable HTTP (remote).
TransportVaries — REST, SDK calls, or inline function execution.
StandardUniversal MCP protocol. Works with any MCP client.
StandardVendor-specific. Different format for each AI provider.
Explore MCP Server Types
Click each server type to see what capabilities it exposes:
📁
Filesystem
Read, write, search files
💾
Database
Query, insert, update data
🌐
API
Wrap any REST or GraphQL API
🖥️
Browser
Navigate, screenshot, interact
🧠
Memory
Persistent knowledge recall
🔍
Search
Web, docs, or code search
Match Server to Use Case
Tap one on the left, then its match on the right