MCP Server Setup With Python and Inspector

Contenido del curso

Introducción a MCP

Conceptos basicos de MCP

MCP avanzado

Integrando tu MCP con un agente

Tomar examen

Cursos Empresas Blog Live Conf Eventos Precios

0:0010:10

MCP Server Setup With Python and Inspector

Curso de MCP con Microsoft Azure

Clase 4 de 22

Clase 4 / 22

Recursos

Setting up an MCP development environment is simpler than it looks. You only need Python, a code editor, and the right pip package to start building your first server, test it with an inspector, and prepare it for a client. Here you will learn the exact workflow to go from an empty folder to a fully running MCP server you can inspect in your browser.

What do you need before installing MCP?

Before touching any code, clarify your tools. The setup is intentionally minimal so you can grow it later.

A code editor of your choice. I use VS Code because I also build regular software, but Eclipse, IntelliJ, Visual Studio or Anthropic's Claude work just as well, especially Claude which is highly compatible with MCP.
A programming language with an official SDK. The course uses Python, but you can build MCP servers with TypeScript, C#, Java or Node.
A terminal where you can run pip and create folders.

What language should I use to build an MCP server? Any language with an official SDK. Python, TypeScript, C#, Java and Node all have one. Pick the one you feel most comfortable with.

The choice of Python here is personal preference, not a technical requirement tied to AI. That distinction matters because it frees you to follow along in whatever stack you already know.

How do you install the MCP CLI with pip?

The first real step is installing the MCP command line interface. This package gives you a global tool you can reuse across every project, so you only install it once.

Inside your working directory, create a folder for the lesson and move into it:

bash mkdir clase-tres cd clase-tres

Then install the package globally:

bash pip install "mcp[cli]"

The brackets around cli are what unlock the command line tooling. Without them you get the library but lose the convenience of running mcp dev or mcp run directly from your terminal.

How do you create your first server.py file?

Open the folder in VS Code with code . and create a file named server.py. The minimum code uses FastMCP, the high level helper that turns regular Python functions into MCP capabilities.

python from mcp.server.fastmcp import FastMCP

mcp = FastMCP("Demo")

@mcp.tool() def add(a: int, b: int) -> int: return a + b

@mcp.resource("greeting://{name}") def greeting(name: str) -> str: return f"Hello, {name}"

Notice two decorators: @mcp.tool exposes a function as a callable tool, and @mcp.resource exposes data the client can read. Both are the building blocks of any server.

How do you test the server with MCP Inspector?

Once you have the file, run the development server from the same folder:

bash mcp dev server.py

The terminal returns a session token and a localhost URL. Hold control and click the link to open MCP Inspector in your browser. This visual tool lets you connect to your server and explore everything it exposes.

What is MCP Inspector? A browser based tool that lists the tools, resources and prompts of an MCP server so you can test them before connecting a real client.

If the connect button throws a connection error, close the session with control plus C and use a more reliable command that prepends the inspector explicitly to mcp run server.py. In my own exercises this version establishes the connection cleanly while the default one sometimes fails silently.

How do you list resources and tools in the inspector?

Once connected, the inspector exposes four useful actions:

List resources, which may appear empty if all your resources use parameters.
List resource templates, where parameterized resources like greeting with a name argument show up.
List tools, where you find functions like add along with the schema the client must follow.
List prompts, another category you can attach to a server.

The red text that sometimes appears is a log, not an error. Reading it carefully prevents unnecessary debugging.

What is the difference between a tool and a resource in MCP? A tool is a function the client can call to perform an action. A resource is data the client can read, often identified by a URI pattern with parameters.

This inspection step is the equivalent of scanning your server's contract. You confirm how each component is structured so that any client connecting later knows exactly what to consume.

What should you practice before the next step?

Before moving on to building a client, extend the server to feel comfortable with both decorators. A good practice set looks like this:

Add tools for subtract, multiply and divide following the same pattern as add.
Expand the greeting resource to accept a full name with multiple parameters.
Re run mcp dev server.py and confirm each new capability appears in the inspector.

Playing with these small variations cements the mental model of tools versus resources and prepares you for the client side, where these definitions become the contract your AI application will rely on. What tools or resources are you planning to add to your first server?

Luis Muniz

Hace un año

Mi experiencia es que si trabajas con Windows en WSL Ubuntu 22.04 deberas tomar en cuenta lo siguiente:

Si tu carpeta de proyecto está en la ruta /mnt/c/Users/... cuando se invoca npm o npx o node se invocan los paquetes de windows y eso da problemas para el Inspector y no se puede conectar. Para solucionarlo esto es lo que hice:

1.- Crear tu carpeta de proyecto en /home/miusuario/CursoMCP/...

2.- Instalar python, pip y venv en el WSL y que no se tome el bridge de windows, como saberlo? con los siguientes comandos:

> which python3 # deberá mostrar /usr/bin/python3

> which node # deberá mostrar /usr/bin/node

> which npm # deberá mostrar /usr/bin/npm

Si muestra rutas que apuntan a las carpetas de windows , esta usando los bridges de WSL y deberas instalar correctamente con:

> sudo apt update && sudo apt upgrade

> sudo apt install -y curl gnupg python3-pip python3-venv

> sudo apt install -y nodejs

Una vez instalado todo, deberas crear en la carpeta de clase3 el venv

> python3 -m venv venv > source venv/bin/activate

con el venv activado instalar mcp[cli]

> pip install "mcp[cli]"

Y con esto deberan poder ejecutar el Inspector

> npx @modelcontextprotocol/inspector mcp run server.py

NOTA: Recuerden antes de presionar Connect, en los campos :

Transport Type -> STDIO
Command -> mcp
Argument -> run server.py

Sebastian Marin

Hace un año

Muchisimas gracias por tomarte el tiempo de escribir todo tan detallado. Fue la unica respuesta que me funciono.

Comentarios (52)52 comentarios

Miguel Angel de la Rosa Manríquez

John J. Meza

Carlos Ruiz Bustillo

Carlos Enrique Ramírez Flores

Diego Bassi

Fredy Flores

Amin Espinoza

Profesor

Alfredo Olmedo

Iván López Hdez

Angel Almazan

Fernado Michael Acosta Panchez

Luis Rodolfo Altuve Cáceres

William Schnaider Torres Bermon

Hugo Rodriguez

Cristian Pisco Intriago

Favio Náquira

Miguel Bastidas

Hace 9 meses

Lilí Primaveral

andres reyes

Ricardo Aviles Sanders

Hace 6 meses

David Herrera

Javier Imbus

Hace 7 meses

Jhonatan Estiven Becerra Pedrozo

Hace 8 meses

Sergio Brandon De Lucio Chavero

Edgar A. Gonzalez Ambriz

Roberto Jacobo

Victor Chavarro

Lester Rodriguez

Agustin Diaz

Karen Paola Torres Archbold

Introducción a MCP

Introducción a MCP

MCP Core Architecture: Server, Client, and Host

MCP Dev Environment Setup for Python

MCP Server Setup With Python and Inspector

Conceptos basicos de MCP

Four Core Blocks of Every MCP Server

Building an MCP Client That Talks to Your Server

Adding an LLM to Your MCP Client

STDIO vs SSE in MCP Servers

LLM Connected to a Local MCP Server

Testing MCP Servers Without a Browser

Deploying an MCP Server to Azure Container Apps

Using MCP Servers in VS Code Agent Mode

MCP avanzado

Query Azure Resources Directly From VS Code

Herramientas avanzadas de MCP para optimizar servidores y seguridad

GPT-4 Reading Local Files via MCP Server

Image Brightness Analysis with MCP and NumPy

How MCP Agents Remember Conversations

Enrutamiento de herramientas con MCP Server

Integrando tu MCP con un agente

Building a Web Search MCP Server with SERP API

Adding News, Products and Q&A Tools to MCP

Why MCP Docs Already Feel Outdated

MCP as the New Standard for AI Systems

MCP Server Setup With Python and Inspector

Progreso del curso

Introducción a MCP

Conceptos basicos de MCP

MCP avanzado

Integrando tu MCP con un agente

Recursos

Recursos