zaDojo: Free MCP for Search Console and Google Analytics, plus SERP and Keyword Research
zaDojo is a free MCP server for Google Search Console and Google Analytics 4. Connect Claude, ChatGPT or Cursor and query your own SEO data at no cost, forever. Add live SERP data and keyword research when you need it, paid per use. Remote endpoint: https://app.zadojo.com/mcp (OAuth).
Server MCP Terhosting
npx add-mcp 'https://app.zadojo.com/mcp'Terpasang ke Claude Code, Codex, Cursor, dan lainnya
Dokumentasi
zaDojo runs a remote MCP server that any client supporting remote MCP can connect to. MCP (Model Context Protocol) is the standard way AI apps call outside tools. Through it, your agent can research keywords, read live Google results, look up any domain's rankings and backlinks, run site audits, track rankings and AI answers, and read your own Search Console and Google Analytics data.
The server address:
https://app.zadojo.com/mcp
The first time a client connects, it opens a zaDojo login in your browser and asks you to approve access. After that, the client can use the tools for the projects you can see. For CI jobs and servers without a browser, use an API key.
Claude Code and Codex users get more from the plugin, which adds this connection and the twelve zaDojo skills in one install. Use the steps on this page when you only want the MCP connection, or when your client has no plugin. The agent setup guide has a prompt that picks the right route for you.
What you need
- A zaDojo account. Sign up to get 100 trial credits with no card.
- A client that supports remote MCP servers over HTTP: Claude Code, Claude Desktop, Cursor, Codex CLI, Codex in the ChatGPT desktop app, ChatGPT with a custom connection, VS Code with Copilot, Windsurf (Devin Desktop), Gemini CLI, Zed, or similar.
- A browser for the sign-in, or an API key for headless use.
The Agent setup page inside the app shows the same address with a copy button. Want to try zaDojo data before you sign up? The free SEO tools need no account.
Connect your client
Claude Code
The Claude Code plugin is the better choice for most people. For the connection alone, run this in a terminal:
claude mcp add --transport http --scope user zadojo https://app.zadojo.com/mcp
--scope user makes zaDojo available in every project on your machine. Use --scope local to limit it to the current repository. Claude Code then prompts you to log in to zaDojo. If the prompt does not appear, run /mcp, select zaDojo and complete the login there.
Claude Desktop
On a paid Claude plan, the zaDojo plugin adds the connection and the skills together. On the Free plan, or for the connection alone, add a custom connector:
- Open Customize > Connectors.
- Click Add or + and choose Add custom connector.
- Paste
https://app.zadojo.com/mcp. - Log in to zaDojo and approve access.
Custom connectors work on Claude Free, Pro, Max, Team and Enterprise. The Free plan allows one custom connector.
Cursor
- Open Customize and go to MCP servers, or edit
~/.cursor/mcp.jsondirectly. - Add the zaDojo entry:
{
"mcpServers": {
"zadojo": {
"url": "https://app.zadojo.com/mcp"
}
}
}
- Save the file and approve the zaDojo login when Cursor asks.
The Cursor guide has a one-click install link and the skills install.
Codex CLI
The Codex plugin adds the connection and the skills together. For the connection alone:
codex mcp add zadojo --url https://app.zadojo.com/mcp
Approve the zaDojo login when it opens. If it does not open, run codex mcp login zadojo.
Codex in the ChatGPT desktop app
The Codex plugin includes the skills as well. For the connection alone:
- Open Codex, then go to Settings > MCP servers > Add server.
- Enter the name
zadojo, pick Streamable HTTP, and pastehttps://app.zadojo.com/mcp. - Save, then click Restart when Codex asks.
- Click Authenticate next to zaDojo and approve the sign-in.
- Open a new Codex chat and run the connection check.
This connection only covers Codex. ChatGPT on the web needs its own. OpenAI's reference is the Codex MCP documentation.
ChatGPT
Add zaDojo as a custom MCP connection with OAuth. It works on ChatGPT Free and paid plans, although workspace admins can block custom connections. The ChatGPT guide walks through every screen.
VS Code, Windsurf and Gemini CLI
Each has its own page with the exact config, API key setup and skills install:
Other MCP clients
Any client that can reach a remote MCP server over streamable HTTP and supports OAuth sign-in can use the address above. If the client cannot do OAuth, send an API key in a header as described next.
| Client | Where to add it | Config |
|---|---|---|
| Zed | Settings > AI > MCP Servers > Add Remote Server | "context_servers": { "zadojo": { "url": "https://app.zadojo.com/mcp" } } |
| Cline | MCP Servers > Remote Servers, or cline mcp add zadojo https://app.zadojo.com/mcp --transport http | "type": "streamableHttp", "url": "https://app.zadojo.com/mcp" |
| opencode | opencode.json | "mcp": { "zadojo": { "type": "remote", "url": "https://app.zadojo.com/mcp" } } |
| Goose | goose configure > Add Extension > Remote Extension (Streamable HTTP) | type: streamable_http, uri: https://app.zadojo.com/mcp |
| Kiro | ~/.kiro/settings/mcp.json | "mcpServers": { "zadojo": { "url": "https://app.zadojo.com/mcp" } } |
| Warp | Settings > Agents > MCP servers > Add > Streamable HTTP or SSE Server (URL) | { "zadojo": { "url": "https://app.zadojo.com/mcp" } } |
| JetBrains Junie | ~/.junie/mcp/mcp.json, then /mcp > Authorize | "zadojo": { "url": "https://app.zadojo.com/mcp" } |
All of these open the zaDojo login in your browser the first time they connect.
Connect with an API key
An API key replaces the browser login. Use one for CI pipelines, remote servers, agents such as Hermes where the login flow does not work, or any client without OAuth support.
A key belongs to you personally. Whatever an agent does with it runs as your account in your workspace, so store it as a secret and never commit it to a repository.
To create one, open API keys under Settings in the zaDojo app and click Create API key. Copy the key right away, because zaDojo shows it only once. Keys start with zadojo_.
Claude Code:
claude mcp add --transport http --scope user zadojo https://app.zadojo.com/mcp --header "Authorization: Bearer zadojo_YOUR_KEY"
Cursor: add a headers block to the zaDojo entry in mcp.json:
{
"mcpServers": {
"zadojo": {
"url": "https://app.zadojo.com/mcp",
"headers": {
"Authorization": "Bearer zadojo_YOUR_KEY"
}
}
}
}
Codex CLI: keep the key in an environment variable and point Codex at it:
export ZADOJO_API_KEY=zadojo_YOUR_KEY
codex mcp add zadojo --url https://app.zadojo.com/mcp --bearer-token-env-var ZADOJO_API_KEY
Any other client: send either Authorization: Bearer zadojo_YOUR_KEY or x-api-key: zadojo_YOUR_KEY with each request.
To revoke a key, open the same API keys section and remove it.
Check the connection
Open a new chat or session and send:
Use zaDojo to check my connection and list my projects.
The agent should call whoami and list_projects. You get back your account, your remaining credit balance and your projects, or an empty list if you have none yet. Both tools are free. If the agent describes MCP instead of calling a tool, the server is not loaded in this session: reload the client or start a new chat.
Available tools
The server has more than 80 tools. The table groups them by job. Tool names are what your agent sees.
| Area | Main tools | Credits |
|---|---|---|
| Account and projects | whoami, list_projects, create_project, get_project_context, update_project_context | Free |
| Keyword research | research_keywords (ideas from 1 to 5 seeds), get_keyword_metrics (volume, difficulty, intent, CPC and trends for up to 700 keywords), search_serp_locations | Paid, except location lookup |
| Google results | get_serp_results (live organic results for 1 to 10 keywords), find_serp_competitors | Paid |
| Domain research | get_domain_overview, get_ranked_keywords, get_domain_keyword_suggestions | Paid |
| Backlinks | get_backlinks_overview, get_backlinks_profile | Paid |
| Saved keywords | list_saved_keywords, save_keywords, remove_saved_keywords | Free |
| Rank tracking | create_rank_tracker, add_rank_tracking_keywords, estimate_rank_tracker_cost, run_rank_tracker, get_rank_tracker, pin_rank_tracking_keywords, remove_rank_tracking_keywords | Checks are paid, setup and reads are free |
| Site audit | run_site_audit, get_audit_status, get_audit_issues, get_audit_pages, list_site_audits, delete_site_audit | Free without Lighthouse or JavaScript rendering |
| Local SEO | search_local_businesses, get_local_serp_results (Maps or Local Finder), get_local_rank_grid, get_business_profile, get_business_reviews, get_business_updates, get_google_business_questions, list_business_categories | Paid, except category lookup |
| Google Search Console | get_search_console_performance, get_search_console_insights (low CTR pages, cannibalized queries, click gains and drops), get_search_console_hourly (the last 48 hours), get_search_console_sitemaps, inspect_urls (up to 10 URLs per call) | Free |
| Google Analytics | get_google_analytics_organic_overview, get_google_analytics_organic_landing_pages, get_google_analytics_page_performance, get_google_analytics_traffic_acquisition, get_google_analytics_key_events, get_google_analytics_ecommerce_performance, get_google_analytics_site_search, get_google_analytics_audience_breakdown, get_google_analytics_measurement_health, get_google_analytics_traffic_overview, get_google_analytics_breakdown, get_google_analytics_realtime_users, get_search_opportunities | Free |
| AI visibility | research_ai_visibility_prompts, explore_prompt, generate_ai_visibility_prompts, save_ai_visibility_tracker, estimate_ai_visibility_cost, set_ai_visibility_schedule, run_ai_visibility_check | Paid |
| AI visibility results | get_ai_visibility_tracker, get_ai_visibility_run, get_ai_visibility_results, get_ai_visibility_answer, get_ai_visibility_sources, get_ai_visibility_trend, export_ai_visibility_data | Free |
| Reports | save_report, list_reports, get_report, delete_report, set_report_sharing, list_report_templates, save_report_template, delete_report_template | Free |
A few behaviours worth knowing:
- Project context is shared memory for a project: business overview, current goal, positioning, writing preferences, competitors, key pages and a research log. Agents read it before they start, and the app and other agents see the same entries.
- Reports saved by an agent appear in the project for your whole team to read, print or export. New reports are private. A public link is created only when you ask the agent to call
set_report_sharingwithpublic: true, andpublic: falserevokes it.get_reportreturnsreport.shareUrlwhen a public link exists, ornullwhen it does not. - Search Console and Google Analytics tools read the property already connected to the project. Access is read-only.
- Estimates come first for anything recurring. Rank tracking and AI tracking both have estimate tools, so the agent can show you the cost before it schedules checks.
What uses credits
Credits come from your zaDojo balance. 1,000 credits equal €1, and paid plans start at €10 a month with 10,000 credits included. Typical prices:
| Action | Typical cost |
|---|---|
| Keyword research search | about 70 credits |
| Domain overview | about 20 credits, about 60 with its top 100 keywords |
| Backlink overview with 12 months of history | about 150 credits |
| Local Maps or Local Finder check | 4 to 7 credits |
| One AI prompt check on one engine | 2 credits scheduled, about 7 run now |
| Prompt Research for one keyword | about 340 credits |
| Tracking 100 keywords weekly on one device | about 5,000 to 9,000 credits a month |
Free: account checks, project context, saved keywords, reports, Search Console, Google Analytics, plain site audits, and reading rank tracking, audit or AI visibility results you already collected. Agents connected to zaDojo are told to ask you before a planned batch above 2,000 credits. When the balance hits zero, paid tools stop until you top up. See pricing for the estimator.
After you connect
The connection gives your agent data. Skills tell it what to do with that data, step by step. If you used MCP without a plugin, install the skills next.
Give the agent one specific job rather than asking it to "do SEO":
- SEO Project Setup: save your goal, positioning, competitors and key pages so every later task starts from them.
- SEO Coach: get one recommended next step if you are new to SEO.
- SEO Audit: find the few changes most likely to grow traffic.
- Keyword Research and Keyword Clustering: find search terms worth targeting and group them into pages.
- Competitive Landscape and Competitor Analysis: map a market, or study one rival in depth.
- Link Prospecting: find sites that might link to a page and draft outreach.
- AI Prompt Research and AI Visibility Audit: see what AI tools say about your market and why competitors get mentioned.
The AI visibility guide covers engines, coverage and costs for AI answer tracking.
Troubleshooting
The client cannot connect. Check that the address is exactly https://app.zadojo.com/mcp, with https:// and no trailing spaces.
Codex reports Authorization server response missing required issuer: expected https://app.zadojo.com. Codex releases 0.143 to 0.146 drop the issuer during OAuth. Update Codex CLI or the Codex desktop app to 0.147.0 or newer, or use an API key.
Sign-in fails or keeps expiring. Remove the zaDojo server from your client, add it again and repeat the login.
The agent cannot find a project. Ask it to call list_projects first and reuse the returned project ID in later calls. If you have no projects, ask it to create one for your domain with create_project, which is free.
A paid tool says you are out of credits. On the paid plan, buy a top-up from billing in the app or wait for your monthly credits to reset. On the trial, subscribe to keep using paid tools.
Still stuck? Email hello@zadojo.com with your client name and version and the exact error. Never include API keys.