local_ai_readiness — SEO Audit MCP Tool
local_ai_readiness
(local ai readiness) is one of 11 tools on the
SEO Audit
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call local_ai_readiness from your client
- Claude Code SEO Audit local_ai_readiness run in your project directory
- Claude Desktop SEO Audit local_ai_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SEO Audit local_ai_readiness ~/.cursor/mcp.json
- VS Code SEO Audit local_ai_readiness .vscode/mcp.json
- Zed SEO Audit local_ai_readiness ~/.config/zed/settings.json
- Windsurf SEO Audit local_ai_readiness ~/.codeium/windsurf/mcp_config.json
- Cline SEO Audit local_ai_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SEO Audit local_ai_readiness ~/.gemini/settings.json
- Grok SEO Audit local_ai_readiness .mcp.json (in your project root)
- ChatGPT SEO Audit local_ai_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai SEO Audit local_ai_readiness Settings → Connectors → Add custom connector
- LangChain SEO Audit local_ai_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http seo-audit https://seoaudit.openkrill.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.