SiteWide

io.github.macminibausPublished by GitHub account macminibausv0.5.0Updated Oct 27, 2026

One MCP connector for GA4, Search Console, Google Ads, Ahrefs, a site crawler and Web Vitals.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote MCP connector that gives an assistant access to GA4, Search Console, Google Ads, Ahrefs, a site crawler and Web Vitals in one place.

What you can do
  • Pull analytics and traffic data from Google Analytics 4 and Search Console.
  • Review Google Ads campaign and advertising data.
  • Look up SEO and backlink data from Ahrefs.
  • Crawl a site and inspect its pages.
  • Check Web Vitals and page performance metrics.
When to use it
Useful when you want an assistant to combine SEO, paid search, analytics and site performance data for one property without wiring up several separate connectors.
Requirements
A remote MCP endpoint reached over streamable HTTP; OAuth sign-in is required, so the relevant Google and Ahrefs accounts must be authorized.
Before you install
OAuth grants the server access to connected Google Ads, Analytics, Search Console and Ahrefs accounts; review the requested scopes before authorizing, and note that query data is sent to the remote service.

Installation

In SourceWeft

  1. Open SiteWide in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.macminibaus%2Fsitewide/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sitewide": {
      "type": "http",
      "url": "https://mcp.alejandrorioja.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.5.0LatestOct 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.