Skip to content
MCP server

PerfBee in Claude and ChatGPT

Ask your AI assistant to crawl your site and explain what is broken. The PerfBee MCP server gives Claude, ChatGPT, Claude Code and Cursor the crawls of the sites in your PerfBee account, with the HTML element each issue sits in.

Last updated: October 17, 2026

Server URL
https://dashboard.perfbee.com/mcp
Transport
Streamable HTTP
Sign-in
OAuth (Claude, ChatGPT) or an API key
In short

Connect an AI app to your PerfBee account once. It can then list your sites, start crawls of them, and read broken links, SEO and AI readiness issues with a short fix for each. It works only on the sites in your My Sites list. Crawls use your credits; reading results is free. You need a PerfBee account: create one for free.

Connect Claude

  1. In Claude, open Customize > Connectors and choose Add custom connector.
  2. Paste the server URL https://dashboard.perfbee.com/mcp. Under Authentication, choose Sign in now.
  3. Add it and choose Connect. Sign in to PerfBee and choose Allow.

On the PerfBee page you also decide whether Claude may start crawls. Without that, it can only read your sites and reports.

Connect ChatGPT

Add PerfBee as an app with the server URL https://dashboard.perfbee.com/mcp, then sign in to PerfBee and choose Allow, as for Claude.

Claude Code, Cursor and other clients

Claude Code can sign in the same way. Add the server, then run /mcp in Claude Code and choose PerfBee to sign in:

Terminal · Claude Code
claude mcp add --transport http perfbee https://dashboard.perfbee.com/mcp

Clients that cannot sign in with OAuth, such as Cursor, use an API key. Create one in the PerfBee dashboard under Settings > API keys. It is shown once. Keep it in an environment variable, not in a file you commit.

Terminal · Claude Code with an API key
claude mcp add --transport http perfbee https://dashboard.perfbee.com/mcp \
  --header "Authorization: Bearer ${PERFBEE_API_KEY}"
Cursor · mcp.json
{
  "mcpServers": {
    "perfbee": {
      "url": "https://dashboard.perfbee.com/mcp",
      "headers": { "Authorization": "Bearer ${env:PERFBEE_API_KEY}" }
    }
  }
}

Other MCP clients connect to the same URL over Streamable HTTP, with the header Authorization: Bearer followed by the key.

What the AI app can do

ToolWhat it doesCredits
list_sitesYour sites in My Sites, each with its latest crawl and schedule, and the credits left this month.No
start_crawlStarts a crawl of a site in My Sites: a full crawl of up to 100 pages unless the app asks for another size, at most 500. Returns at once.Yes, per page checked
get_scan_statusThe progress or result of a crawl: pages and links checked, broken and not-checked counts, credits charged.No
get_scan_issuesBroken links and resources with the page and HTML element they sit in, page SEO issues and AI readiness issues, each with a short fix.No
get_ai_readinessThe AI Search Readiness report of a full crawl: which AI crawlers robots.txt lets in, and the page issues that keep pages out of AI answers.No
compare_crawlsWhat changed since the previous crawl of the site: new, gone and changed pages, new and fixed broken links.No

A crawl started by an AI app is an ordinary PerfBee crawl. It shows in your dashboard with its full report, and it is charged the way a crawl you start yourself is. Pages a site refuses are counted as not checked and are not charged. There are no tools to add or remove sites, change schedules or delete anything.

Limits

  • Crawls only of sites in your My Sites list. To crawl another site, add it in the dashboard first.
  • At most 500 pages per crawl. Larger crawls run from the dashboard.
  • 10 crawls a day per connected app or API key, 20 a day per workspace, and 2 running at the same time.
  • 60 tool calls a minute per connected app or API key.
  • A crawl needs enough credits for all the pages it may check before it starts.

Your data and permissions

  • An app you connect acts for your workspace with your role. If you are a viewer, it can only read. If you leave the workspace, it stops working.
  • The results of the tools you call go to the AI app and its provider, under your own agreement with them. PerfBee does not send them anywhere else.
  • We store a hash of each API key and sign-in token, never the key itself. For each call we log the time, the tool and whether it worked, not the conversation.
  • See your connected apps and keys in Settings > API keys. Disconnecting an app or revoking a key stops it at once.
  • Crawls follow the rules on our crawler page: the same user agent, address and signature as every other PerfBee crawl.

Details are in our Privacy Policy and Terms of Service.

Troubleshooting

  • “This app could not be identified”: PerfBee's sign-in works with Claude, Claude Code and ChatGPT. Other clients use an API key.
  • The site is not in My Sites: add it in the dashboard, then ask again.
  • The app keeps asking you to sign in: disconnect it in Settings > API keys and connect it again.
  • Not enough credits: ask for fewer pages, or see your credits in Usage & Billing.

Contact

Questions about the MCP server: [email protected].