> 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/data-for-llms/what-is-model-context-protocol-mcp-and-how-does-it-benefit-web-api-usage.md).

# What is Model Context Protocol (MCP), and how does it benefit Web API usage?

Learn what the Model Context Protocol is and how it connects AI agents to Web API.

Model Context Protocol (MCP) is a standard way for AI models and agents to connect to external tools and data sources.

Before MCP, connecting an LLM to a web data source took a custom integration for each one. That led to complex solutions that were hard to scale.

With the Oxylabs MCP server for [Web API](https://developers.oxylabs.io/products/web-api), any MCP client, such as Claude Code or Cursor, can search the web, read pages as Markdown, extract fields as JSON, and call dedicated scrapers directly. You don't need to write or maintain integration code.

🧠 To set it up, see the [MCP server documentation](https://developers.oxylabs.io/ai-workflows/mcp) and [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/data-for-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.