check_wordpress_agent_readiness — Site Passport MCP Tool Read-only
check_wordpress_agent_readiness
(check wordpress agent readiness) is one of 1 tool on the
Site Passport
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_wordpress_agent_readiness from your client
- Claude Code Site Passport check_wordpress_agent_readiness run in your project directory
- Claude Desktop Site Passport check_wordpress_agent_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Site Passport check_wordpress_agent_readiness ~/.cursor/mcp.json
- VS Code Site Passport check_wordpress_agent_readiness .vscode/mcp.json
- Zed Site Passport check_wordpress_agent_readiness ~/.config/zed/settings.json
- Windsurf Site Passport check_wordpress_agent_readiness ~/.codeium/windsurf/mcp_config.json
- Cline Site Passport check_wordpress_agent_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Site Passport check_wordpress_agent_readiness ~/.gemini/settings.json
- Grok Site Passport check_wordpress_agent_readiness .mcp.json (in your project root)
- ChatGPT Site Passport check_wordpress_agent_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai Site Passport check_wordpress_agent_readiness Settings → Connectors → Add custom connector
- LangChain Site Passport check_wordpress_agent_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http check-wordpress-agent-readiness https://sitepassport.org/.well-known/mcp.json
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.