Audits websites for search engine optimization, AI answer visibility, and agent accessibility using a browser extension and CLI.
Also known as WorkPodsAgents/agent-ready, agent-ready, @workpods/agent-ready
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.1
- Last commit
- Nov 9, 2026
- License
- Apache-2.0
What is Agent Ready MCP?
Agent Ready audits websites for search engine optimization, AI answer visibility, and agent accessibility using a browser extension and CLI.
Summary generated from the project's README
About Agent Ready MCP server
Agent Ready by WorkPods provides a local MCP server and CLI designed to audit websites for search engine optimization, AI answer visibility, and agent accessibility. Developers can use this tool to inspect how AI agents interact with web content through page, site-file, and crawl checks. It works by running a local server over stdio, which can be integrated into clients like Claude Desktop, Cursor, or Claude Code using npx commands.
The system functions through a combination of a Node.js environment and a Chrome browser extension. While basic checks like inspecting robots.txt, sitemaps, and llms.txt can run in Node without the extension, advanced features like inspecting rendered text, WebMCP tools, and agent journeys require the browser extension to be active. Users can also perform research tasks involving keyword gaps and backlinks by connecting a DataForSEO provider account within the extension settings.
What you can do with it
- 1Verify AI answer visibilityAnalyze how a brand is mentioned and cited within an open AI assistant tab.
- 2Perform SEO and keyword researchIdentify keyword ideas and link gaps using external data providers.
- 3Test agent task journeysObserve how an agent performs specific steps on a page within a scratch tab.
Written from the project's README. Every use case is checked against a quote from it.
How to install Agent Ready MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Agent Ready MCP in Claude Code
$ claude mcp add agent-ready -- npx -y @workpods/agent-readyInstall Agent Ready MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"agent-ready": {
"command": "npx",
"args": [
"-y",
"@workpods/agent-ready"
]
}
}
}Install Agent Ready MCP in VS Code
.vscode/mcp.json
{
"servers": {
"agent-ready": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@workpods/agent-ready"
]
}
}
}Install Agent Ready MCP in VS Code CLI
$ code --add-mcp '{"name":"agent-ready","type":"stdio","command":"npx","args":["-y","@workpods/agent-ready"]}'Install Agent Ready MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"agent-ready": {
"command": "npx",
"args": [
"-y",
"@workpods/agent-ready"
]
}
}
}Install Agent Ready MCP in Codex
$ codex mcp add agent-ready -- npx -y @workpods/agent-readyInstall Agent Ready MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.agent-ready] command = "npx" args = ["-y", "@workpods/agent-ready"]
Install Agent Ready MCP in Gemini CLI
$ gemini mcp add -s user agent-ready npx -- -y @workpods/agent-readyInstall Agent Ready MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"agent-ready": {
"command": "npx",
"args": [
"-y",
"@workpods/agent-ready"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableworkpodsagents/agent-ready is public and reachablegithub.com/workpodsagents/agent-ready ↗Pass
- Package names this repository as its source@workpods/agent-ready names workpodsagents/agent-ready as sourcenpmjs.com/package/@workpods/agent-ready ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-09github.com/workpodsagents/agent-ready ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @workpods/agent-readyPass
- No critical advisory in the package or its dependencies120 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@workpods/agent-ready
Local MCP server and CLI for the Agent Ready browser extension: check SEO, AI answer visibility (GEO), and whether AI agents can use a website (AXO).
Install the extension
Install Agent Ready from the Chrome Web Store.
The extension provides rendered-page checks, reads from open AI answer tabs, and agent journeys. Page, site-file, and crawl checks can also run in Node without the extension.
Quick start
Requires Node.js 22 or later. Print the installed package version:
npx -y @workpods/agent-ready --version
Check one page and its site files:
npx -y @workpods/agent-ready check https://example.com --fail-on high
The command prints a Markdown report. It exits with code 1 if a check fails or partly fails at
high or critical severity. Checks that need a browser are reported as not applicable. Running
npx -y @workpods/agent-ready without a subcommand prints usage and exits with code 2.
Use from an AI agent
In the extension's Settings → Agent connection, enable Connect to the local bridge when it runs. Keep Chrome open while the agent works.
For Claude Code:
claude mcp add agent-ready -- npx -y @workpods/agent-ready mcp
For Cursor (~/.cursor/mcp.json) or Claude Desktop (claude_desktop_config.json), add this to
the client's MCP settings:
{
"mcpServers": {
"agent-ready": {
"command": "npx",
"args": ["-y", "@workpods/agent-ready", "mcp"]
}
}
}
The client starts the local server over stdio. See agent setup for Codex, skills, and Firefox origin configuration.
What it can do
- Page and site checks: audit a page, crawl a site, and inspect robots.txt, sitemaps, llms.txt, and agent manifests.
- Agent visibility: inspect rendered text, accessible controls, and WebMCP tools; compare two pages. Requires the extension.
- AI answers: read an answer already open in a supported AI assistant tab and report brand mentions and citations. Requires the extension; it does not send a prompt.
- Research: find keyword ideas, keyword gaps, backlinks, and link gaps through DataForSEO. Requires the extension and your own provider account; usage may incur charges.
- Journeys: observe a page and take steps in a scratch tab to test an agent task. Requires the extension. Final submissions, purchases, and sign-ins are refused.
No WorkPods account is required. Provider keys stay in the extension; the MCP server returns results to the agent and does not receive those keys.
Links
Agent Ready by WorkPods · Source code · Privacy and permissions · CLI documentation · Apache-2.0 license
Built by WorkPods. Written by Shefali Munjal. See LICENSE and NOTICE for licensing and attribution.
Agent Ready MCP questions
How do I add Agent Ready MCP to Claude Code?
Run claude mcp add agent-ready -- npx -y @workpods/agent-ready in your terminal. Add --scope user to make it available in every project.
How do I add Agent Ready MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does using this server require a WorkPods account?
No, a WorkPods account is not required to use the service.
Can the tool perform purchases or sign-ins during agent journeys?
No, the tool refuses to perform final submissions, purchases, or sign-ins during journey testing.
What is required to inspect AI answers in a browser tab?
To read answers from a supported AI assistant tab, you must have the Agent Ready browser extension installed.