Skip to content

Cline MisarSEO MCP Server start_site_audit

How to: Cline MisarSEO MCP Server start_site_audit

client:Cline transport:streamable-http tool:start_site_audit

Add MisarSEO MCP Server to Cline

  1. 01

    Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "misarseo-mcp": {
      "url": "https://api.misar.io/seo/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cline.

  2. 03

    Ask for something start_site_audit does. Cline lists the server's tools on connect and calls start_site_audit itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that MisarSEO MCP Server's identifier in your config matches the one above exactly.

Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs

Set these first

MisarSEO MCP Server will not start until these are set, so start_site_audit never becomes available.

  • MISARSEO_API_KEY
  • MISARSEO_BASE_URL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 17 October 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.