DataZen Documentation
DataZen User Guide

AI Client Remote MCP Settings

DataZen can be configured as a remote MCP server so compatible AI clients such as Microsoft Copilot, Cursor, and Claude Desktop can discover and call pipelines exposed as MCP tools. The client connects directly to a DataZen HTTP endpoint; no local npm package or stdio MCP server is required.

This direct connection uses the MCP Streamable HTTP transport, with MCP messages encoded using JSON-RPC 2.0. Client configuration screens generally call this a Remote MCP server, HTTP server, or Streamable HTTP connection rather than a JSON-RPC connection.

When to Use This Connection

Remote MCP connectivity currently supports the Agent → Pipeline use case only. It lets an AI client invoke Reader or Direct pipelines that have been exposed as MCP tools. It does not currently replace the npm-based REST configuration for DataZen API Tools.

Use this model when the client supports remote MCP servers. It is the recommended option for pipelines as tools because configuration requires only the MCP endpoint and authentication, rather than a local command, npm package, and environment variables.

Prerequisites

  • An administrator must issue a Service Token with the mcp_all scope. See Security Overview.
  • At least one Reader or Direct pipeline must have Enable this pipeline as an LLM Tool selected in its MCP Tool settings.
  • The AI client must support a remote MCP server over HTTP / Streamable HTTP.

DataZen MCP Endpoint

  • Self-hosted agent — connect to <agent-url>/mcp.
  • iPaaS cloud agent — connect to <environment-url>/{agentid}/api/mcp.

Authentication

DataZen supports only Token-based authentication when servicing MCP tools. This requirement applies to all AI clients. Send the Service Token in the HTTP Authorization header using this exact format: 

Authorization: Token <ServiceToken>

The Token prefix, including the space after it, is required before the Service Token value. DataZen does not currently support OAuth 2.0 for MCP authentication.

The Service Token must include the mcp_all scope. See Security Overview for instructions to create and manage Service Tokens. Do not place a token in a shared or source-controlled configuration file.

Microsoft Copilot

When registering the remote MCP server in Copilot, choose API Key as the authentication mechanism and configure the API key as an HTTP header:

  • Header — Authorization
  • Value — Token <ServiceToken>

Make sure the value begins with Token ; do not enter only the raw Service Token.

Terminology in Microsoft Copilot

Microsoft and GitHub documentation describe this as connecting to a remote MCP server. In VS Code and GitHub Copilot configuration, select an HTTP server and provide its URL; HTTP uses the Streamable HTTP transport. Copilot Studio similarly describes the supported transport as Streamable.

Related Topics