Ask your assistant about audit issues, rankings, Quick Wins and uptime in plain language, using live data from your projects instead of pasted exports.
MCP, the Model Context Protocol, is a standard that lets AI assistants call tools and read data. The BigRank MCP server exposes your project data so an assistant can answer questions about your SEO without you copying anything.
The server gives assistants read access to the project data you already see in the app. Apps sign in to a workspace, and editors use a workspace key, so answers come from your own crawls, rank checks and monitors.
Your assistant connects to one URL and gets ten tools it can call during a conversation, each with a description of what it answers.
The ChatGPT and Claude apps add the URL as a connector and sign in. Settings → API shows the setup for Claude Code, Gemini CLI, Cursor and VS Code.
Assistants read the newest crawl with results unless you name one, plus rankings, Quick Wins, uptime, Core Web Vitals and backlinks.
An app signs in to the one workspace you choose, and a key reads only its own workspace, so neither reaches another team's projects.
Every tool reads project data. Your assistant answers questions about the numbers, and you decide what to change on your site.
Signed JSON to your URL for every alert, with retries, ready for n8n and Zapier.
Skip the spreadsheet step. Ask which issues the latest crawl found, which keywords dropped or how many Quick Wins are open, and get an answer grounded in your latest data.
Connect the assistant you already use for chat, coding or analysis, so SEO context is there where the work happens.
Start your own workflows in n8n or Zapier when a crawl finishes, a site goes down or a ranking drops. Every alert is sent as signed JSON to your URL.
Connecting takes one URL in your assistant and a sign-in or a workspace key. After that, questions about a project are answered from its current data, and the changes on your site stay yours to make.
In ChatGPT or Claude, add a custom connector with the URL from Settings → API. In Claude Code, Gemini CLI, Cursor or VS Code, copy the setup from the same page.
Apps ask you to sign in and choose a workspace. Editors take a workspace key in the header.
Ask about issues, rankings, Quick Wins or uptime for one of your projects.
Make the change on your site, then ask again after the next crawl.
The MCP server suits work that already happens inside an assistant or an editor, where bringing SEO facts into the conversation saves a trip to the dashboard and a pasted export.
An assistant in your editor lists the pages with an issue, so you can fix them in the same session.
An assistant summarizes the latest crawl, ranking moves and monitor status.
Combine your Quick Wins counts and rankings with an assistant's drafting help.
Teams pull project facts into the tools they already work in, connected to each client's workspace.
SEO MCP brings project data into your assistant; Project Workspace organizes projects and access, and Quick Wins ranks the fixes an assistant would bring up.
Connect ChatGPT, Claude, Cursor, VS Code and other MCP clients to your audit issues, rankings and Quick Wins.
Keep every site as a project, give teammates and clients the right role, and get alerts for crawls, downtime and ranking drops.
See ranked SEO opportunities from Search Console and crawl data, each with why it matters and what to change.
Keep going
The MCP server answers from your projects' data. Run an audit, track keywords and set up monitors so there is something to ask about.
Answers about which clients work, sign-in from the Claude and ChatGPT apps, rate limits, the REST API, workspace scoping, and whether an assistant can change your site.
The ChatGPT and Claude apps connect by signing in. Claude Code, Gemini CLI, Cursor and GitHub Copilot in VS Code have exact setups in Settings → API, and any other client that sends an Authorization header works the same way.
Yes. Each workspace's plan allows a number of requests per minute, and the MCP server shares that limit with the REST API.
Yes. Create a key in workspace Settings → API to read projects, audits, rankings and monitoring data, start crawls and add Rank Tracker keywords.
No. A sign-in covers the one workspace you choose, and each key reads a single workspace.
Yes. Add a custom connector with the server URL, sign in, and choose a workspace. You can see and revoke connected apps in Settings → API.
No. Every tool only reads project data such as issues, rankings and Quick Wins. Changes to your site stay with you.
Plans start at $19/month with a 7-day free trial. Every plan includes the site audit, Search Console insights and white-label reports.