The CData Code Assist MCP for Google Search defines each connection to Google Search as a named configuration that an MCP Client (such as Claude Desktop) can use when sending natural language queries.

You create and manage these configurations using the CData Code Assist MCP Configuration Tool. The tool automatically handles formatting, storage, and registration with MCP clients.

Understanding Connection Configurations

Each connection configuration is stored in a .mcp file. This file includes the details needed to initialize the connector when an MCP Client starts a session.

• On Windows, configuration files are stored in "~/AppData/Roaming/CData/Google Search Data Provider/".
• On macOS, configuration files are stored in "~/Library/Application Support/CData/Google Search Data Provider/".

The .mcp file is a text file that contains a list of connection properties and a timestamp. For example:

#Tue May 20 15:48:40 EDT 2025
AuthScheme=Basic
User=myUser
Password=myPassword
Security Token=myToken

The configuration tool handles these settings automatically. Each saved configuration enables an MCP client to launch a dedicated MCP server instance with the correct connector and options. Manual file editing is not required.

Connecting to Google Search

Provide the following connection properties before adding the authentication properties.

• CustomSearchId: Obtain this value by signing into Google Custom Search Engine and creating a new search engine.
• APIKey: You must enable the Custom Search API in the Google API Console.

For more information on obtaining values for these properties, refer to Connecting to Google Search.