What Rabbot's MCP server is

What MCP means here

MCP is a standard way for an AI agent, such as Claude, to call tools that answer questions about your store. Rabbot runs its own MCP server, mounted in the same app that already watches your pages and your product feeds. Once you mint a token, any MCP-capable agent can ask it things like “what is blocking sales on my store right now” and get back a real answer, drawn from your live data.

Agent access is free on every plan, including the free one.

What it gives your agent

The server holds nine tools. Eight of them only read: they answer questions about your protection status, your open issues, one page’s history, and what Rabbot has caught and confirmed fixed. One tool writes: it can mark a finding as intentional so Rabbot stops flagging it, and it refuses on anything blocking a sale, with two documented exceptions that can be intentional: a deliberate password gate or a custom purchase flow.

The agent gets Rabbot’s judgment, not a raw list of rows to sort through itself. Ask “what’s blocking sales” and the answer names the problem, already grouped by product and newest first, instead of handing back every page on your store for the agent to work out on its own.

What Rabbot adds

Two things: a decision about what counts as a problem, and a record of what your pages looked like before today. An agent starting from raw store data has to make the first call itself, and it can only see the state in front of it.

Rabbot already recorded that history. A page’s timeline goes back seven days on the free tier and further on paid plans, so the agent can answer “when did this start” without having to have been watching since day one.

Getting started

You need a token from Settings > Agent access (MCP) in your installed app, and a client that can send it as a bearer header. The next two articles cover minting a token and connecting your agent, whether that is Claude Code or another MCP-capable client.