Connecting Mastra with PingOne Data via CData Connect AI MCP Server

Mastra is designed for developers and enterprise teams building intelligent, composable AI agents. Its modular framework and declarative architecture make it simple to orchestrate agents, integrate LLMs, and automate data-driven workflows. But when agents need to work with data beyond their local memory or predefined APIs, many implementations rely on custom middleware or scheduled syncs to copy data from external systems into local stores. This approach adds complexity, increases maintenance overhead, introduces latency, and limits the real-time potential of your agents.

CData Connect AI bridges this gap with live, direct connectivity to more than 300 enterprise applications, databases, ERPs, and analytics platforms. Through CData's remote Model Context Protocol (MCP) Server, Mastra agents can securely query, read, and act on real-time data without replication. The result is grounded responses, faster reasoning, and automated decision-making across systems all with stronger governance and fewer moving parts.

This article outlines the steps required to configure CData Connect AI MCP connectivity, register the MCP server in Mastra Studio, and build an agent that queries live PingOne data in real time.

Prerequisites

Before starting, make sure you have:

1. A CData Connect AI account
2. Node.js 18+ and npm installed
3. A working Mastra project (created via npm create mastra@latest)
4. Access to PingOne

Credentials checklist

Ensure you have these credentials ready for the connection:

1. USERNAME: Your CData email login
2. PAT: Connect AI, go to Settings and click on Access Tokens (copy once)
3. MCP_BASE_URL: https://mcp.cloud.cdata.com/mcp

Step 1: Configure PingOne connectivity for Mastra

Connectivity to PingOne from Mastra is made possible through CData Connect AI Remote MCP. To interact with PingOne data from Mastra, we start by creating and configuring a PingOne connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "PingOne" from the Add Connection panel

3. Enter the necessary authentication properties to connect to PingOne.

   To connect to PingOne, configure these properties:

   • Region: The region where the data for your PingOne organization is being hosted.
   • AuthScheme: The type of authentication to use when connecting to PingOne.
   • Either WorkerAppEnvironmentId (required when using the default PingOne domain) or AuthorizationServerURL, configured as described below.

   Configuring WorkerAppEnvironmentId

   WorkerAppEnvironmentId is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

   First, find the value for this property:

   1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
   2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
   3. In the environment's home page navigation sidebar, click Applications.
   4. Find your OAuth or Worker application details in the list.
   5. Copy the value in the Environment ID field. It should look similar to:
      

      WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

   Now set WorkerAppEnvironmentId to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   AuthorizationServerURL is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

   Authenticating to PingOne with OAuth

   PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

   • Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
   • To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
   • Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

   OAuth (Authorization Code grant)

   Set AuthScheme to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • InitiateOAuth: GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the OAuthAccessToken each time you connect, use InitiateOAuth.
   • OAuthClientId: The Client ID you obtained when you created your custom OAuth application.
   • OAuthClientSecret: The Client Secret you obtained when you created your custom OAuth application.
   • CallbackURL: The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

   When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

   1. The driver obtains an access token from PingOne and uses it to request data.
   2. The OAuth values are saved in the location specified in OAuthSettingsLocation, to be persisted across connections.

   The driver refreshes the access token automatically when it expires.

   For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add PingOne Connection page and update the User-based permissions.

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Mastra. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, we are ready to connect to PingOne data from Mastra.

Step 2: Set up the Mastra project

• Open a terminal and navigate to your desired folder
• Create a new project:

  npm create mastra@latest


• Open the folder in VS Code
• Install the required Mastra dependencies:

  npm install @mastra/core @mastra/libsql @mastra/memory

• Then install the MCP integration package separately:

  npm install @mastra/mcp

Step 3: Configure environment variables

Create a .env file at the project root with the following keys:

OPENAI_API_KEY=sk-...
[email protected]
CDATA_CONNECT_AI_PASSWORD=your_PAT

Restart your dev server after saving changes:

npm run dev

Step 4: Add the CData Connect AI agent

Create a file src/mastra/agents/connect-ai-agent.ts with the following code:

import { Agent } from "@mastra/core/agent";
import { Memory } from "@mastra/memory";
import { LibSQLStore } from "@mastra/libsql";
import { MCPClient } from "@mastra/mcp";

const mcpClient = new MCPClient({
  servers: {
    cdataConnectAI: {
      url: new URL("https://connect.cdata.com/mcp/"),
      requestInit: {
        headers: {
          Authorization: `Basic ${Buffer.from(
            `${process.env.CDATA_CONNECT_AI_USER}:${process.env.CDATA_CONNECT_AI_PASSWORD}`
          ).toString("base64")}`,
        },
      },
    },
  },
});

export const connectAIAgent = new Agent({
  name: "Connect AI Agent",
  instructions: "You are a data exploration and analysis assistant with access to CData Connect AI.",
  model: "openai/gpt-4o-mini",
  tools: await mcpClient.getTools(),
  memory: new Memory({
    storage: new LibSQLStore({ url: "file:../mastra.db" }),
  }),
});

Step 5: Update index.ts to register the agent

Replace the contents of src/mastra/index.ts with:

import { Mastra } from "@mastra/core/mastra";
import { PinoLogger } from "@mastra/loggers";
import { LibSQLStore } from "@mastra/libsql";
import { connectAIAgent } from "./agents/connect-ai-agent.js";

export const mastra = new Mastra({
  agents: { connectAIAgent },
  storage: new LibSQLStore({ url: "file:../mastra.db" }),
  logger: new PinoLogger({ name: "Mastra", level: "info" }),
  observability: { default: { enabled: true } },
});

Step 6: Run and verify the connection

Start your Mastra server:

npm run dev



Step 7: Run a live query in Mastra Studio

In Mastra Studio, open the chat interface and enter one of the following sample prompts:

List available catalogs from my connected data sources.



Build real-time, data-aware agents with Mastra and CData

Mastra and CData Connect AI together enable powerful AI-driven workflows where agents have live access to enterprise data and act intelligently without sync pipelines or manual integration logic.

Start your free trial today to see how CData can empower Mastra with live, secure access to hundreds of external systems.