Integrate Cursor with Live SAP Ariba Source Data via CData Connect AI

Cursor is an AI-powered code editor that embeds conversational and agent-style assistance alongside your development workflow. By extending Cursor with MCP (Model Context Protocol) tools, you can give its AI agents secure access to external systems such as APIs and databases.

Integrating Cursor with CData Connect AI via the built-in MCP server allows the editor's AI to query, analyze, and act on live SAP Ariba Source data without copying data into the IDE. The result is a development experience where you can chat with your governed enterprise data directly from Cursor.

This article outlines how to configure SAP Ariba Source connectivity in Connect AI, generate the required access token, register Connect AI's MCP Server in Cursor, and then use the AI chat pane to explore live SAP Ariba Source data.

Step 1: Configure SAP Ariba Source connectivity for Cursor

Connectivity to SAP Ariba Source from Cursor is made possible through CData Connect AI's Remote MCP Server. To interact with SAP Ariba Source data from Cursor, start by creating and configuring a SAP Ariba Source connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a connection in Connect AI

2. Select SAP Ariba Source from the Add Connection panel
👁 Selecting data source

3. Enter the necessary authentication properties to connect to SAP Ariba Source.

   In order to connect with SAP Ariba Source, set the following:

   • API: Specify which API you would like the provider to retrieve SAP Ariba data from. Select the Supplier, Sourcing Project Management, or Contract API based on your business role (possible values are SupplierDataAPIWithPaginationV4, SourcingProjectManagementAPIV2, or ContractAPIV1).
   • DataCenter: The data center where your account's data is hosted.
   • Realm: The name of the site you want to access.
   • Environment: Indicate whether you are connecting to a test or production environment (possible values are TEST or PRODUCTION).

   If you are connecting to the Supplier Data API or the Contract API, additionally set the following:

   • User: Id of the user on whose behalf API calls are invoked.
   • PasswordAdapter: The password associated with the authenticating User.

   If you're connecting to the Supplier API, set ProjectId to the Id of the sourcing project you want to retrieve data from.

   Authenticating with OAuth

   After setting connection properties, you need to configure OAuth connectivity to authenticate.

   • Set AuthScheme to OAuthClient.
   • Register an application with the service to obtain the APIKey, OAuthClientId and OAuthClientSecret.

     For more information on creating an OAuth application, refer to the Help documentation.

   Automatic OAuth

   After setting the following, you are ready to connect:

   APIKey: The Application key in your app settings. OAuthClientId: The OAuth Client Id in your app settings. OAuthClientSecret: The OAuth Secret in your app settings.

   When you connect, the provider automatically completes the OAuth process:

   1. The provider obtains an access token from SAP Ariba and uses it to request data.
   2. The provider refreshes the access token automatically when it expires.
   3. The OAuth values are saved in memory relative to the location specified in OAuthSettingsLocation.
   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions
👁 Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Cursor. It is best practice to create a separate PAT for each integration to maintain granular access control.

1. Click the gear icon () at the top right of the Connect AI app to open Settings
2. On the Settings page, go to the Access Tokens section and click Create PAT
3. Give the PAT a descriptive name and click Create
👁 Creating a new PAT

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 SAP Ariba Source connection configured and a PAT generated, Cursor can now connect to SAP Ariba Source data through Connect AI.

Step 2: Configure Connect AI in Cursor

Next, configure Cursor to use Connect AI. Cursor reads MCP configuration from an mcp.json file in the user configuration directory and exposes the registered servers under the Tools & MCP settings. Once configured, Cursor's AI chat can call the tools exposed by CData Connect AI.

1. Download the Cursor desktop application and complete the sign-up flow for your account
2. From the top menu, click Settings to open the settings panel 👁 Opening Cursor Settings
   
3. In the left navigation, open the Tools & MCP tab and click Add Custom MCP 👁 Tools & MCP tab with Add Custom MCP
   
4. Cursor opens an mcp.json file in the editor
5. Add the following configuration. Make sure to base64-encode your email:PAT before inserting into the header:

   {
    "mcpServers": {
    "cdata-mcp": {
    "url": "https://mcp.cloud.cdata.com/mcp",
    "headers": {
    "Authorization": "Basic your_base64_encoded_email_PAT"
    }
    }
    }
   }
   		

   👁 Configuring mcp.json with Connect AI
   
6. Save the file
7. Return to Settings and then select Tools & MCP. You can now see cdata-mcp enabled with an active indicator 👁 Connect AI enabled
   

Step 3: Chat with CData Connect AI from Cursor

1. From the top bar, click Toggle AI Pane to open the chat window 👁 Opening the AI pane
   
2. Test the connection by entering "List connections"
3. You can also run queries like "Query SAP Ariba Source data and list the high priority accounts" 👁 Querying SAP Ariba Source data from Connect AI
   

Cursor is now fully integrated with the CData Connect AI MCP Server and can act on live SAP Ariba Source data directly from the editor.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your development tools, try CData Connect AI today!