Google Search By Cdata MCP Server

:heavy_exclamation_mark: This project builds a local, read-only MCP server. For fully remote MCP access, check out the first managed MCP platform

Remote serverstreamable-http

What is the Google Search By Cdata MCP server?

Google search by cdata mcp server lets Claude, Cursor and other MCP clients work with Google Search By Cdata directly. :heavy_exclamation_mark: This project builds a local, read-only MCP server. For fully remote MCP access, check out the first managed MCP platform: CData Connect AI. For locally hosted, full read, write, update, delete, and action capabilities and a simplified setup.

What Google Search By Cdata does

:heavy_exclamation_mark: This project builds a local, read-only MCP server. For fully remote MCP access, check out the first managed MCP platform: CData Connect AI. For locally hosted, full read, write, update, delete, and action capabilities and a simplified setup, check out our CData MCP Server for Google Search. ## Purpose We created this read-only MCP Server to allow LLMs (like Claude Desktop) to query live data Google Search supported by the CData JDBC Driver for Google Search.

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

  • source_get_tables — The source_get_tables tool exposed by this server
  • source_get_columns — The source_get_columns tool exposed by this server
  • source_run_query — The source_run_query tool exposed by this server

Installing the google search by cdata mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Google Search By Cdata sits in that group, and the shape of its toolset — source_get_tables, source_get_columns, source_run_query — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
  • Maintained by CDataSoftware.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the google search by cdata mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
source_get_tablesThe source_get_tables tool exposed by this server.
source_get_columnsThe source_get_columns tool exposed by this server.
source_run_queryThe source_run_query tool exposed by this server.

How to install the Google Search By Cdata MCP server

**Linux/Mac**
      ```json
      {
        "mcpServers": {
          "{classname_dash}": {
            "command": "/PATH/TO/java",
            "args": [
              "-jar",
              "/PATH/TO/CDataMCP-jar-with-dependencies.jar",
              "/PATH/TO/google-search.prp"
            ]
          },
          ...
        }
      }

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Google Search By Cdata to source get tables.
  • Use Google Search By Cdata to source get columns.
  • Use Google Search By Cdata to source run query.

Frequently asked questions

It connects Google Search By Cdata to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (source_get_tables, source_get_columns, source_run_query) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Google Search By Cdata directly.