Integrate Goose with Live Sage 300 Data via CData Connect AI

Goose is an open source AI agent that runs locally on your machine and works with a wide range of LLM providers. It supports the model context protocol (MCP) through its extensions framework, so you can add external tools and data sources and give the agent access to live systems beyond the model's training data.

By integrating Goose with CData Connect AI through the built-in MCP Server, Goose gains governed, real-time access to live Sage 300 data. You can list catalogs, explore schemas, and query records from Sage 300 data using natural language prompts, with all data access running securely against authorized sources.

This article explains how to configure Sage 300 connectivity in Connect AI, generate the required personal access token, install and set up Goose, add the Connect AI MCP Server as a custom extension, and verify the integration by querying live Sage 300 data from the Goose chat.

Step 1: Configure Sage 300 connectivity for Goose

Connectivity to Sage 300 from Goose is made possible through Connect AI's Remote MCP Server. To interact with Sage 300 data from Goose, start by creating and configuring a Sage 300 connection in Connect AI.

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

2. Select Sage 300 from the Add Connection panel

3. Enter the necessary authentication properties to connect to Sage 300.

   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.
   
4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Goose. 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

4. Copy the token when displayed and store it securely. It will not be shown again

With the Sage 300 connection configured and a PAT generated, Goose can now connect to Sage 300 data through Connect AI.

Step 2: Install and set up Goose

Next, install Goose, choose an LLM provider, and add the Connect AI Remote MCP Server as a custom extension so the agent can discover and call live data tools through Connect AI.

1. Download and install Goose by following the official installation guide, then launch the application
2. On the Welcome to goose screen, choose an AI provider. Select Use Free/Local Providers to run a local model, or Connect to a Provider to configure a provider such as OpenAI, Anthropic, or Google, and enter the required API key
3. In the left navigation, click Extensions, then click + Add custom extension
4. In the extension dialog, configure the server with the following values:
   • Extension Name: CData MCP, or any name of your choice
   • Type: Streamable HTTP
   • Endpoint: https://mcp.cloud.cdata.com/mcp
5. Under Request Headers, add the following two headers and click + Add after each pair:
   • Authorization: Basic your_base64_encoded_email_PAT
   • Content-Type: application/json

   Note: Goose will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier in the format email:PAT, base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ789, the Authorization header value becomes something like: Basic dXNlckBkb21haW4uY29tOkFCQzEyMy4uLlhZWjc4OQ==

   
6. Click Save to save the configuration
7. Return to the chat, click the extensions icon at the bottom of the chat input, and confirm that the configured MCP is enabled

With the MCP server added and an LLM provider configured, Goose is ready to query live Sage 300 data through Connect AI.

Step 3: Query live Sage 300 data from Goose

With the integration complete, use the Goose chat to interact with live Sage 300 data through natural language prompts handled by the configured LLM.

1. With the CData MCP extension enabled, type a prompt in the chat, for example:
   • List catalogs from my CData MCP
   • Show the available schemas and tables for Sage 300
   • Query the top 5 records from a table in Sage 300 data
2. Goose calls the Connect AI MCP Server and returns live results from Sage 300 data

At this point, your Goose agent communicates with the Connect AI MCP Server and retrieves live Sage 300 data through remote MCP tools directly from the chat.

Get CData Connect AI

To access hundreds of SaaS, big data, and NoSQL sources directly from your cloud applications, try CData Connect AI today. Download a free 14-day trial of CData Connect AI, and our Support Team is available to help with any questions you have.