> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/help-center/es/datos-para-llms/what-is-model-context-protocol-mcp-and-how-does-it-benefit-web-api-usage.md).

# ¿Qué es Model Context Protocol (MCP) y cómo beneficia el uso de Web API?

Aprende qué es Model Context Protocol y cómo conecta agentes de IA con Web API.

El Protocolo de Contexto de Modelo (MCP) es una forma estándar para que los modelos y agentes de IA se conecten a herramientas externas y fuentes de datos.

Antes de MCP, conectar un LLM a una fuente de datos web requería una integración personalizada para cada una. Eso daba lugar a soluciones complejas que eran difíciles de escalar.

Con el servidor MCP de Oxylabs para [Web API](https://developers.oxylabs.io/products/web-api), cualquier cliente MCP, como Claude Code o Cursor, puede buscar en la web, leer páginas como Markdown, extraer campos como JSON y llamar directamente a scrapers dedicados. No necesitas escribir ni mantener código de integración.

🧠 Para configurarlo, consulta la [documentación del servidor MCP](https://developers.oxylabs.io/ai-workflows/mcp) y [GitHub](https://github.com/oxylabs/web-api-mcp).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.oxylabs.io/help-center/es/datos-para-llms/what-is-model-context-protocol-mcp-and-how-does-it-benefit-web-api-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.