Get started with Open Agentic Kit (closed beta)

This guide walks through connecting your MCP client to Open Agentic Kit (OAK). For a rundown of what OAK can do, see Open Agentic Kit overview.

NOTE: OAK access is currently available to select partners in closed beta. To register your interest, contact your account representative at The Trade Desk.

What you need to know

Here's what you need to know about authentication and access control:

• Every request runs through The Trade Desk standard authorization layer. Your agent sees exactly the data you would see in the platform UI—nothing more, regardless of what it asks for.
• You can scope tokens to specific capabilities—for example, data access without modification permissions.
• Most MCP clients also let you set approval requirements per action type, independent of the platform-enforced review step described under Configuration & Management in the Capabilities section. For example, you can allow read-only actions to run automatically while requiring an explicit approval step before any modification is executed.

Authentication methods

OAK supports the following authentication methods.

Configure your MCP client

There are multiple methods to use OAK:

• Claude Desktop
• Copilot Studio
• Manual configuration

Depending on your configuration, you must meet the following requirements:

Be approved as an OAK private beta partner. To register your interest, contact your account representative at The Trade Desk.
Have an MCP-compatible AI client. For AI assistant or chatbot integrations, you can use a host or agent platform.
Have access to the production or sandbox OAK MCP servers.
For application-to-application integrations, you can connect an MCP client using the client's official SDK, if available.
If you use Enterprise Claude, confirm with your IT team whether they need to configure the connector for you.
If your application does not support CIMD, generate an API token from your account settings. See also Authentication methods.

Configure your Claude Desktop client

To add the OAK server using the Claude Desktop application, follow these steps:

1. Go to Settings and select "Connectors"
2. Select the "Add" dropdown and choose "Add custom connector".
3. Enter the corresponding OAK MCP servers for production or sandbox data.

Configure your Copilot Studio client

IMPORTANT: Before you can perform these steps, you must have a client ID and secret key. Contact your account manager for details.

To add the OAK server to your Copilot Studio application, follow these steps:

1. Open Copilot Studio and select "Agents" from the sidebar.
2. Select an existing agent, or create a new agent if the list is empty.
3. Go to the "Tools" page, and select "Add a tool".
4. Choose the "Model Context Protocol (MCP)" tool type.
5. Create a connection to the corresponding OAK MCP servers for production or sandbox data.
   NOTE: To connect with multiple environments, create a new agent.
6. Select "Create" and then "Next".
7. Enter your client ID and client secret key.
8. Save your agent's tool by selecting "Add and configure".

Manual configuration in client file

Add the OAK server to your MCP client configuration and pass your API token in the request header.

NOTE: The config file location varies by MCP client. For details, refer to the documentation for your tool.

{
  "mcpServers": {
    "ttd-open-agentic-kit-koa": {
      "url": "MCP_SERVER_URL_PLACEHOLDER"
    }
  }
}

OAK MCP servers

There are MCP environments that have access based on our The Trade Desk environments. The following table lists the servers that host the Koa Agent system.

Next steps

When connected, your AI agent discovers available OAK capabilities automatically. No further setup is required. For ideas on how to start querying, see Example prompts and Ask Koa tool.