Connecting the MCP
The Rubric MCP is a hosted service that lets your own AI assistant read your Rubric results and act on them. You connect it with an API key generated on the MCP page in Rubric, then point an MCP-compatible AI client at the hosted MCP endpoint. Once connected, your assistant can pull your scores, pillars and issues, and it can start a crawl or lint a draft on your behalf, so you can run the whole fix loop without leaving the assistant.
- →The hosted Rubric MCP lets your AI assistant read your Rubric results and act on them: it can start a crawl, re-crawl after a fix, and check a draft.
- →You connect it using an API key generated on the MCP page in Rubric.
- →It cannot change your account, settings or billing, and it only ever reads your own data.
What is the Rubric MCP?
MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to an external tool or data source. The Rubric MCP is a hosted MCP built on that standard. It gives an MCP-compatible AI client a way to read your Rubric results directly and to run crawls and draft checks for you, so you can work your citability from inside the assistant you already use, rather than copying numbers out of the report by hand.
The host never scores your site: the Rubric engine computes every number deterministically, and the MCP returns what the engine produced. Your assistant reads those results and can ask Rubric to run a new crawl, but it is never the thing doing the scoring.
How to connect the MCP
Connecting comes down to generating a key and giving it to your AI client.
What your assistant can do
Once connected, an AI assistant can read the same results Rubric shows you: your page scores against the 70 line, the pillar breakdown across Known, Findable and Trusted, and the open issues behind each check. It can also act on them: start a crawl, re-crawl a site after you ship a fix, and lint a draft before you publish. That means you can ask your assistant to run the whole loop, find your weakest pillar, make the top fix, re-crawl, and compare the before and after, and it works from your real Rubric data.
The MCP returns results; it does not recompute them. The scores it shows are from the latest crawl of that site, so ask it to re-run a crawl (or run one in Rubric) when you want fresh numbers.
What the MCP cannot do
The MCP can read your results and run crawls and draft checks, but it cannot change your account: it cannot edit a setting, change your plan or billing, delete your data, or create or change a share link. Every account change stays inside Rubric, done by you. And an API key only ever reaches your own data, never anyone else's.
MCP, Copy for AI and CSV: when to use which
Rubric gives you three ways to take your results elsewhere, and they suit different needs.
| Method | Best for |
|---|---|
| MCP | Letting your own AI assistant read your live Rubric results and run the fix loop on demand |
| Copy for AI | Copying your money queries as text to paste into an AI tool for a quick test |
| CSV export | Pulling scores and failing checks into a spreadsheet or your own tracker |
For the text-paste route, use Copy for AI in the report. For spreadsheets, export to CSV and Sheets. The related articles cover both, and what Rubric checks explains what the results themselves mean.