> 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/consume/v1/consume-with-ai/connect-an-agentic-framework/custom.md).

# Custom

Connect any agentic framework to Data Product MCP using streamable HTTP.

## Prerequisites

Your DataOS instance URL, a [DataOS API token](/consume/v1/get-started/before-you-begin.md), and a framework that can connect to MCP tools over streamable HTTP. See [API tokens](https://v2.dataos.info/references/key-concepts/api-tokens) for how tokens work.

## Connect

Configure your framework with these values, replacing `<API_TOKEN>`:

| Field        | Value                                           |
| ------------ | ----------------------------------------------- |
| Server name  | `DataProduct-MCP`                               |
| Transport    | Streamable HTTP                                 |
| URL          | `https://<instance-url>/dataproduct-mcp/api/v1` |
| Header key   | `apikey`                                        |
| Header value | `<API_TOKEN>`                                   |

You can copy these from **Home → Connect to Data Product MCP** in DataOS. Most MCP client libraries accept a server definition shaped like this:

```json
{
  "DataProduct-MCP": {
    "transport": "http",
    "url": "https://<instance-url>/dataproduct-mcp/api/v1",
    "headers": { "apikey": "<API_TOKEN>" }
  }
}
```

Adapt the syntax to your framework's MCP adapter. For framework-specific examples, see [LangChain](/consume/v1/consume-with-ai/connect-an-agentic-framework/langchain.md) or [Vercel AI SDK](/consume/v1/consume-with-ai/connect-an-agentic-framework/vercel-ai-sdk.md).

## Verify

List the available tools from `DataProduct-MCP`, then ask the agent `What data products am I authorized to access?`. A working connection returns products scoped to your token and permissions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://v2.dataos.info/consume/v1/consume-with-ai/connect-an-agentic-framework/custom.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.