gaseo — SEO Issue Tracker (MCP Server)

Tracks Google Search Console issues per project and exposes them as MCP tools for AI agents. Data is stored locally in ~/.gaseo/gaseo.db (SQLite — no database server required).

Quick Install

Add to your MCP config (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "gaseo": {
      "command": "npx",
      "args": ["-y", "@lyriryl/gaseo"]
    }
  }
}

Then authenticate once (see below). That's it — works on any machine.

Authentication

gaseo uses Google OAuth to read your@ Search Console data. You need to do this once per machine.

Step 1 — Create OAuth credentials in Google Cloud Console:

1. Go to console.cloud.google.com/apis/credentials
2. Click Create Credentials → OAuth 2.0 Client ID
3. Application type: Desktop app
4. Download the JSON file

Step 2 — Authenticate:

npx @lyriryl/gaseo auth /path/to/downloaded-credentials.json

This opens a URL in your terminal. Open it in your browser, authorize gaseo, paste the code back. Tokens are saved to ~/.gaseo/oauth-tokens.json.

Step 3 — Grant GSC access: Make sure the Google account you authorized owns (or has access to) the Search Console property you want to track.

New machine setup

Run npx @lyriryl/gaseo auth again with your credentials file. The ~/.gaseo/oauth-tokens.json file is the only state that needs to move — copy it from your old machine or re-authenticate.

Available Tools

| Tool | Description | |------|-------------| | register_project | Onboard a new site. Run once per project. | | list_projects | Show all managed projects and their last sync time. | | get_actionable_seo_issues | Get open issues. Auto-syncs from GSC if data is >24h stale. | | mark_issue_fixed | Mark an issue fixed. Pings IndexNow and your sitemap webhook. | | push_indexnow_update | Manually submit a URL to Bing/Yandex/Yahoo via IndexNow. |

HTTP/SSE server (multi-client use)

For Copilot, remote agents, or shared access:

npm start        # Listens on port 3000 (or PORT env var)

Connect at http://localhost:3000/mcp/sse.