liveBook · Manning

MCP server

An MCP server is a software component that implements the Model Context Protocol to expose tools, data, or other capabilities to compatible clients.

How 12 Manning books explain it

Spring AI in Action

An MCP server is an application component that communicates through the Model Context Protocol to expose capabilities or contextual information to an MCP client.

How it is used
Exposes reusable tools, prompts, and resources so LLM applications can access capabilities beyond the model itself.
How deep it goes
Builds servers from Spring Boot setup through tool registration, inspection, client integration, transports, prompts, and resources; defers Streamable HTTP.
Examples
Uses filesystem access, board-game database queries, MCP Inspector invocations, and structured game prompts and resources.
What you can do after
Build it from scratch with Spring AI, test it with MCP Inspector, and connect it to an LLM application over STDIO or HTTP+SSE.

Read how Spring AI in Action explains MCP server →

AI Agents in Action, Second Edition

An MCP server is a service that exposes tools, prompts, and resources to AI applications through the Model Context Protocol.

How it is used
Uses MCP servers as reusable integration boundaries for agent actions and shared capabilities.
How deep it goes
Works through tool registration, client connection, deployment choices, lifecycle management, and operational trade-offs.
Examples
Illustrates research-source and journal tools, plus a Brave Search server configured with an API key.
What you can do after
Apply MCP via FastMCP and Claude Desktop to expose and connect a simple tool.

Read how AI Agents in Action, Second Edition explains MCP server →

Grokking AI Applications

An MCP server is a service that implements the Model Context Protocol to expose tools and related capabilities to compatible clients or agents.

How it is used
Connects assistants and applications to reusable tools through a standard discovery-and-invocation protocol.
How deep it goes
Explains tool reuse, governance, automatic Langflow setup, and Python client-server mechanics including handshake, discovery, and invocation.
Examples
Uses enterprise assistants, culinary travel flows, a calculator server, stdio communication, and embedded website chat.
What you can do after
Build it from scratch with FastMCP, expose tools, connect a client, list capabilities, and invoke selected tools programmatically.

Read how Grokking AI Applications explains MCP server →

Build AI-Enhanced Web Apps

An MCP server is a server-side program that implements the Model Context Protocol and exposes tools, prompts, and resources to clients or AI applications.

How it is used
Exposes reusable external capabilities to AI applications through a standardized client–server interface.
How deep it goes
Works through server registration, an API-backed tool, stdio communication, client integration, and operational considerations.
Examples
Uses a Next.js chat app, a public jokes API, a registered tool, and MCP Inspector testing.
What you can do after
Build it from scratch with the MCP SDK, then connect and test it through the Vercel AI SDK and MCP Inspector.

Read how Build AI-Enhanced Web Apps explains MCP server →

AI Agents and Applications

An MCP server is a service endpoint that exposes tools through the Model Context Protocol.

How it is used
Standardizes how agents discover and use service capabilities without individually wrapping each service.
How deep it goes
Works through server construction, client integration, and verification while leaving prompts and other shared resources for further study.
Examples
Builds an AccuWeather server and replaces a travel agent’s mock weather tool with live data.
What you can do after
Build an MCP server with FastMCP 2 and integrate its tools into an agent using MultiServerMCPClient.

Read how AI Agents and Applications explains MCP server →

Hugging Face in Action

An MCP server is a software service that implements the Model Context Protocol to expose data or executable capabilities to AI assistants and clients.

How it is used
Bridges AI assistants and applications to external data sources and executable tools through a standardized interface.
How deep it goes
Explains components, JSON-RPC communication, transports, Python construction, testing, configuration, and client integration without deeper protocol internals.
Examples
Demonstrates weather retrieval, file and PDF access, temperature conversion, prompts, location lookup, and Claude Desktop workflows.
What you can do after
Build an MCP server in Python, validate it with MCP Inspector, configure it for Claude Desktop, and connect third-party servers.

Read how Hugging Face in Action explains MCP server →

Build an AI Agent (From Scratch)

An MCP server is a protocol component that exposes tools, executes requested tools, and returns their results, potentially by connecting to external services or data.

How it is used
Connects agent tool decisions to discoverable, executable tools and external services through an MCP client.
How deep it goes
Explains discovery and execution, then implements and verifies a decorated Python tool; focuses on tools rather than prompts or resources.
Examples
Uses the official Tavily server and a custom search_web server to demonstrate discovery and web search.
What you can do after
Apply FastMCP to register a Python function as a server tool and verify it with an MCP client.

Read how Build an AI Agent (From Scratch) explains MCP server →

Building LLM Applications with DSPy

A component that exposes tools or data to an MCP client through the Model Context Protocol.

How it is used
Provides a shared tool interface between agents and existing external services or knowledge bases.
How deep it goes
Explains server registration and client discovery through an implementation, focusing on tools rather than resources or reusable prompts.
Examples
Uses a WixQA server with article search and retrieval tools, then connects it to a DSPy support agent.
What you can do after
Apply it via FastMCP and DSPy to expose backend operations and discover them in a ReAct agent.

Read how Building LLM Applications with DSPy explains MCP server →

Authorization in Action

An MCP server is a software component that exposes tools and data-source capabilities through the Model Context Protocol.

How it is used
Connects AI applications to external tools and data sources while supporting structured agent operations.
How deep it goes
Explains discovery, schemas, API translation, and result handling, but stops short of defining authorization decisions.
Examples
Uses document search, calendar access, database queries, workflow actions, and a customer-document JSON tool schema.
What you can do after
Apply structured tool exposure to integrate agents with multiple systems without custom integration code for each one.

Read how Authorization in Action explains MCP server →

Introduction to Generative AI, Second Edition

An MCP server is a component that exposes selected data sources, services, prompt templates, and executable tools through the Model Context Protocol.

How it is used
Connects language models with selected organizational data, services, prompts, and tools through a standardized interface.
How deep it goes
Defines exposed resources and gives concrete examples, but stops short of implementation details or protocol mechanics.
Examples
Uses Splunk queries, cloud-provider logs, log analysis prompts, and time-based log filtering as concrete examples.
What you can do after
Apply MCP through a client to query monitoring data and invoke tools using natural-language requests.

Read how Introduction to Generative AI, Second Edition explains MCP server →

Building Reliable AI Systems

An MCP server is a server component that implements the Model Context Protocol and exposes tools or data capabilities to compatible AI applications.

How it is used
Connects AI applications to external tools or data through a shared interface instead of one-off integrations.
How deep it goes
Traces tool discovery, schema exchange, execution, and results, but does not detail protocol internals.
Examples
Uses a CSV product catalog, a vest-search request, and an email-tool schema to illustrate server tools.
What you can do after
Build and expose a product-search server, then connect it to an AI runtime for tool discovery and execution.

Read how Building Reliable AI Systems explains MCP server →

Building Distributed Applications that Work

An MCP server is a software component that exposes tools, resources, or contextual information to a language model through the Model Context Protocol.

How it is used
Connects a coding assistant to an Aspire instance so it can inspect services, diagnose problems, and work with resources.
How deep it goes
Defines the client-server interaction and lists Aspire tools, while treating the available tool list as non-exhaustive.
Examples
Uses service discovery, resource commands, logs, traces, integration documentation, and app-host selection as tool examples.
What you can do after
Configure an Aspire MCP server for a coding assistant and use its tools to inspect and work with the Aspire instance.

Read how Building Distributed Applications that Work explains MCP server →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.