![]() |
VOOZH | about |
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 Paylocity 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 Paylocity 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 Paylocity data.
Connectivity to Paylocity from Cursor is made possible through CData Connect AI's Remote MCP Server. To interact with Paylocity data from Cursor, start by creating and configuring a Paylocity connection in CData Connect AI.
Set the following to establish a connection to Paylocity:
This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.
Paylocity will decrypt the AES key using RSA decryption.
It is an optional property if the IV value not provided, The driver will generate a key internally.
You must use OAuth to authenticate with Paylocity. OAuth requires the authenticating user to interact with Paylocity using the browser. For more information, refer to the OAuth section in the Help documentation.
The Pay Entry API is completely separate from the rest of the Paylocity API. It uses a separate Client ID and Secret, and must be explicitly requested from Paylocity for access to be granted for an account. The Pay Entry API allows you to automatically submit payroll information for individual employees, and little else. Due to the extremely limited nature of what is offered by the Pay Entry API, we have elected not to give it a separate schema, but it may be enabled via the UsePayEntryAPI connection property.
Please be aware that when setting UsePayEntryAPI to true, you may only use the CreatePayEntryImportBatch & MergePayEntryImportBatchgtable stored procedures, the
InputTimeEntry table, and the OAuth stored procedures. Attempts to use other features of the product will result in an error. You must also store your OAuthAccessToken
separately, which often means setting a different OAuthSettingsLocation when using this connection property.
π Configuring a connection (Salesforce is shown)
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.
With the Paylocity connection configured and a PAT generated, Cursor can now connect to Paylocity data through Connect AI.
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.
{
"mcpServers": {
"cdata-mcp": {
"url": "https://mcp.cloud.cdata.com/mcp",
"headers": {
"Authorization": "Basic your_base64_encoded_email_PAT"
}
}
}
}
π Configuring mcp.json with Connect AICursor is now fully integrated with the CData Connect AI MCP Server and can act on live Paylocity data directly from the editor.
To access hundreds of SaaS, Big Data, and NoSQL sources directly from your development tools, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial