Connect InspectWP to Claude, ChatGPT & Cursor (MCP)

Connect InspectWP directly to Claude, ChatGPT, or Cursor via the Model Context Protocol (MCP) and let the AI assistant generate and analyze WordPress reports on its own.

The Model Context Protocol (MCP) lets you connect InspectWP directly to AI assistants like Claude, ChatGPT, or Cursor. The assistant can then start WordPress analyses, fetch reports, and explain the results in plain language — without you opening the dashboard.

Short version: Create an API token in the API dashboard, add the endpoint URL https://inspectwp.com/api/mcp as a custom connector in your AI client, and supply the token as a Bearer token. Done.

1. Requirements

  • An InspectWP account with an active API plan (Premium accounts include an API quota).
  • An API token — create it in the API dashboard. It starts with iwp_ and is shown only once.
  • An AI client that supports remote MCP: Claude (Pro/Max/Team/Enterprise), ChatGPT (Plus/Pro/Business, Developer Mode), or Cursor.

2. The endpoint URL

All clients use the same URL:

https://inspectwp.com/api/mcp

Authentication is via a Bearer token in the Authorization header, i.e. Authorization: Bearer iwp_your_token.

3. Setup in Claude

  1. Open claude.ai or Claude Desktop and go to Settings → Connectors.
  2. Click Add custom connector and paste the endpoint URL above.
  3. Under Request headers, add the header Authorization with the value Bearer iwp_your_token.
  4. Save — the four InspectWP tools are now available in the chat.

4. Setup in ChatGPT

  1. In ChatGPT, enable Developer Mode under Settings → Connectors.
  2. Add a new connector with the endpoint URL above.
  3. Supply the Bearer token and save. ChatGPT connects over HTTPS — no local server or tunnel needed.

5. Setup in Cursor

  1. In Cursor, open ~/.cursor/mcp.json (or Settings → MCP → Add new server).
  2. Add an HTTP server with the endpoint URL and the Authorization header.
  3. Save and reload Cursor — InspectWP appears in the MCP server list.

6. Available tools

  • generate_report — analyzes one or more WordPress sites (up to 5 per call).
  • get_report — fetches an existing report by its ID.
  • get_me — shows account info and the active API plan.
  • get_usage — shows quota and usage history.

7. Example prompts

Once the connector is active, you can ask your assistant things like:

  • "Analyze example.com with InspectWP and summarize the most important security issues."
  • "Generate reports for these three domains and compare their WordPress versions."
  • "How many reports do I have left this month?"

8. Frequently asked questions

Does a report via MCP use my quota? Yes — every successful report counts against your monthly API quota, just like the REST API. Failed crawls are refunded automatically.

Is the token safe? Treat it like a password. You can revoke it and create a new one anytime in the API dashboard.

Why don't I need an npm package anymore? The hosted endpoint talks to clients directly. A local package is only needed for clients that support local servers exclusively.

Related articles