> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/interfaces/ai-activation/mcp-components.md).

# MCP components

Understand the MCP host, client, server, tools, resources, and prompts used in AI activation.

MCP uses a host-client-server model. In AI activation, these components let a model use Data Product capabilities safely.

## Core components

| Component | Meaning in MCP                                                                      | Example in AI activation                                                                        |
| --------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Host      | The application that provides the user experience and contains the model.           | Cursor, Claude, Copilot in VS Code, ChatGPT Desktop (Codex), or a custom agentic application.   |
| Client    | The protocol connector created by the host for a specific MCP server.               | The MCP connection configured inside the assistant for Data Product MCP.                        |
| Server    | The endpoint that exposes MCP capabilities.                                         | Data Product MCP hosts tools for building, discovering, querying, and inspecting Data Products. |
| Tools     | Callable operations the model can request through the client.                       | Operations for building, discovering, querying, and inspecting Data Products.                   |
| Resources | Read-only context a server can expose when supported by the implementation.         | Documentation, metadata, examples, schema context, or other reference material.                 |
| Prompts   | Reusable prompt templates a server can expose when supported by the implementation. | Guided prompts for investigation, metric validation, or builder workflows.                      |

## Why the client matters

A host can connect to many MCP servers at once. Each connection uses its own client.

The client handles four jobs:

1. Connects to one MCP server.
2. Negotiates supported capabilities.
3. Lists the tools available to the model.
4. Sends tool calls when the model needs external context or action.

A host may connect to Data Product MCP and a separate code or ticketing server in the same session. The host chooses which connection to use based on the user's prompt and the model's plan.

## What stays authoritative

The assistant is the interaction surface. It is not the authority on the data.

Data Product MCP is the controlled bridge. The Data Product remains the system of record for semantics, contracts, policies, quality, lineage, ownership, and runtime access.


---

# 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://v2.dataos.info/references/interfaces/ai-activation/mcp-components.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.
