@misar/seo-mcp exposes MisarSEO research and management actions to MCP clients (Claude Desktop, IDEs, agents) over stdio. It reads MISARSEO_API_KEY and optional MISARSEO_API_URL (default https://api.misar.io/seo) from the environment and calls the same api.misar.io/seo/* surface documented here.

Configuration

{
  "mcpServers": {
    "misarseo": {
      "command": "npx",
      "args": ["@misar/seo-mcp"],
      "env": { "MISARSEO_API_KEY": "your_key" }
    }
  }
}

Tools

Tool	Purpose	Charges credits
`seo_list_projects`	List projects; call first to obtain a `projectId`.	No
`seo_keyword_research`	Expand seeds into keyword ideas with volume/difficulty/CPC.	Yes
`seo_crawl`	Start a site audit crawl.	Yes
`seo_crawl_results`	Fetch crawl/audit results.	No
`seo_rank_check`	Run / read a rank check.	Yes
`seo_rank_tracker_create`	Create a rank-tracker config (domain + schedule).	No
`seo_ai_radar`	AI brand-radar scan (enqueued async).	Yes
`seo_gsc`	Query Google Search Console performance.	No

Entry point

Every tool that needs a projectId expects one from seo_list_projects. Agents should call it before any project-scoped action.

MCP Server

Configuration

Tools