Build Sage 300-Powered Applications in GitHub Copilot with CData Code Assist MCP
GitHub Copilot is an AI-powered coding assistant that integrates directly into Visual Studio Code and other IDEs. With support for MCP, GitHub Copilot can connect to local tools and enterprise data sources, enabling natural language interaction with live systems during development.
Model Context Protocol (MCP) is an open standard for connecting LLM clients to external services through structured tool interfaces. MCP servers expose capabilities such as schema discovery and live querying, allowing AI agents to retrieve and reason over real-time data safely and consistently.
In this article, we guide you through installing the CData Code Assist MCP for Sage 300, configuring the connection to Sage 300, connecting the Code Assist MCP add-on to GitHub Copilot, and querying live Sage 300 data from within Visual Studio Code.
Prerequisites
- Visual Studio Code is installed on your machine
- GitHub Copilot Chat extension is enabled in Visual Studio Code
- CData Code Assist MCP for Sage 300 has been installed
Step 1: Download and install the CData Code Assist MCP for Sage 300
- To begin, download the CData Code Assist MCP for Sage 300
- Find and double-click the installer to begin the installation
- Run the installer and follow the prompts to complete the installation
When the installation is complete, you are ready to configure your Code Assist MCP add-on by connecting to Sage 300.
Step 2: Configure the connection to Sage 300
- After installation, open the CData Code Assist MCP for Sage 300 configuration wizard
NOTE: If the wizard does not open automatically, search for "CData Code Assist MCP for Sage 300" in the Windows search bar and open the application.
- In MCP Configuration > Configuration Name, either select an existing configuration or choose
to create a new one
- Name the configuration (e.g. "cdata_sage300") and click OK
-
Enter the appropriate connection properties in the configuration wizard
Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.
- Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the
option under Security Groups (per each module required). - Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
- Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.
Authenticate to Sage 300 using Basic authentication.
Connect Using Basic Authentication
You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.
- Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
- User: Set this to the username of your account.
- Password: Set this to the password of your account.
- Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the
- Click Connect to authenticate with Sage 300
- Click Save & Test to finalize the connection
This process creates a .mcp configuration file that GitHub Copilot will reference when launching the Code Assist MCP add-on. Now with your Code Assist MCP add-on configured, you are ready to connect it to GitHub Copilot.
Step 3: Connect the Code Assist MCP add-on to GitHub Copilot
- Download and install Visual Studio Code and enable the GitHub Copilot Chat extension
- Open or create the mcp.json file:
- For global configuration: %%APPDATA%%/Roaming/Code/User/mcp.json
- For project-specific configuration:
/.vscode/mcp.json
- Add the JSON code shown below and save the file
- After saving and testing your connection in the configuration wizard, click Next
- Select Github Copilot from the AI MCP Tool dropdown
- Follow the MCP Client Instructions to create the required configuration file
- Copy the displayed JSON code and paste it into your configuration file
Option 1: Manually add the MCP configuration
{
"servers": {
"cdata_sage300": {
"command": "C:\Program Files\CData\CData Code Assist MCP for Sage 300\jre\bin\java.exe",
"args": [
"-Dfile.encoding=UTF-8",
"-jar",
"C:\Program Files\CData\CData Code Assist MCP for Sage 300\lib\cdata.mcp.sage300.jar",
"cdata_sage300"
]
}
}
}
NOTE: The command value should point to your Java 17+ java.exe executable, and the JAR path should point to the installed CData Code Assist MCP add-on .jar file. The final argument must match the MCP configuration name you saved in the CData configuration wizard (e.g. "cdata_sage300").
Option 2: Copy the MCP configuration from the CData Code Assist MCP for Sage 300 UI
Step 4: Query live Sage 300 data in GitHub Copilot
- Launch Visual Studio Code and open the GitHub Copilot Chat interface. Select the tool icon to enable the configured Code Assist MCP add-on
- Ask questions about your Sage 300 data using natural language. For example:
"List all tables available in my Sage 300 data data connection."
- Start building with natural language prompts:
For my project, data from the OEInvoices is very important. Pull data from the most important columns like InvoiceUniquifier and ApprovedLimit.
GitHub Copilot is now fully integrated with CData Code Assist MCP for Sage 300 and can use the MCP tools to explore schemas and execute live queries against Sage 300.
Build with Code Assist MCP. Deploy with CData Drivers.
Download Code Assist MCP for free and give your AI tools schema-aware access to live Sage 300 data during development. When you're ready to move to production, CData Sage 300 Drivers deliver the same SQL-based access with enterprise-grade performance, security, and reliability.
Visit the CData Community to share insights, ask questions, and explore what's possible with MCP-powered AI workflows.