Uninstall Google Search Console MCP
Remove the global CLI and its entry from your MCP client. Your other client servers remain in place. Revoking Google access and deleting local credentials are separate optional steps.
Remove the MCP client entry
- Quit or stop the MCP client.
- In its MCP settings or config file, remove only the
gscserver entry, orgsc-localif you added a generic template with that name. - Save the settings and restart the client.
Optional: revoke Google access
If you want to revoke the OAuth grant, do it before uninstalling the CLI or deleting local data:
Revoke Google access and remove the saved OAuth session
gsc auth revoke --yesTo remove only the local OAuth session without revoking access at Google, run gsc auth logout before uninstalling. Neither command removes service-account key files. For service-account access, disable or delete its key in Google Cloud and remove the account from each Search Console property's user list.
Revoking the OAuth grant can also sign you out of other sessions that use the same app.
Remove the global package
Use the package manager you chose during installation. Removing the package does not delete your Google tokens, profiles, or client configurations.
Uninstall with npm
npm uninstall -g @sonnivasquez/gsc-mcpUpdating instead? Install again with the same command to update without touching your tokens or client setup. See Update or reinstall.
Optional: remove local credentials and data
If you want to remove saved change history, OAuth tokens, profiles, OAuth client files, and service-account keys, delete the data directory after you uninstall. This action is permanent.
~/.gsc-mcpdirectory. If you configured GSC_DATA_DIR, use that exact directory instead. Keys or credentials stored elsewhere are not removed.Delete the default local data directory
rm -rf ~/.gsc-mcp