Search Analytics (Google Search Console & Analytics 4) MCP server

This MCP Search Analytics Server implements the Model Context Protocol to provide unified access to Google Analytics 4 and Google Search Console data. It enables real-time analytics queries with secure credential management through a simple server interface.

Setup Prerequisites

Before installing the MCP server, ensure you have:

• Python 3.8 or higher
• A Google Cloud Project with Analytics and Search Console APIs enabled
• A Google Service Account with appropriate permissions

Installation

Step 1: Clone the Repository

git clone <your-repo-url>
cd mcp-search-analytics

Step 2: Create a Virtual Environment

python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate

Step 3: Install Dependencies

pip install -r requirements.txt

Configuration

Creating Environment File

Start by creating an environment file from the template:

cp environment.example .env

Setting Up Google Service Account

1. Create a service account in Google Cloud Console
2. Download the JSON credentials file
3. Enable the Google Analytics Reporting API and Search Console API
4. Grant the necessary permissions to your service account

Configuring Environment Variables

Edit the .env file with your actual values:

ANALYTICS_CREDENTIALS_PATH=/path/to/your/credentials.json
GSC_SITE_URL=https://your-website.com
GA4_PROPERTY_ID=your-property-id

Usage

Testing Your Credentials

Before running the server, test that your credentials are working:

python test_credentials.py

Running the MCP Server

Start the server with:

python unified_analytics_server.py

Security Best Practices

When using this server, remember to:

• Never commit credential files (.json, .env) to version control
• Store credentials securely and use environment variables
• Regularly rotate service account keys
• Follow the principle of least privilege for API access

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "mcp-search-analytics" '{"command":"python","args":["unified_analytics_server.py"]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "mcp-search-analytics": {
            "command": "python",
            "args": [
                "unified_analytics_server.py"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "mcp-search-analytics": {
            "command": "python",
            "args": [
                "unified_analytics_server.py"
            ]
        }
    }
}

3. Restart Claude Desktop for the changes to take effect