On this page
How to use Layzr MCP
Bring your website audits, AI visibility checks, and search data into your AI assistant.
Updated September 14, 2026
MCP stands for Model Context Protocol. It gives an AI assistant a way to call tools and read data from services you connect. With Layzr MCP, you can ask your assistant to audit a page, retrieve a saved report, or explore your search performance.
One connection uses your existing Layzr account. Your subscription determines the tools available, and usage is shared with the Layzr website. There is no separate MCP subscription.
What you can do with it
- Audit a public website for design, copy, SEO, UX, and conversion issues. Read the report and ask about a fix.
- Find saved audits, mark fixes as planned or applied, and recheck an applied fix.
- Check AI visibility and brand mentions with the providers included in your plan. Run and save custom prompts.
- Manage website workspaces, configure page monitoring, and check what changed.
- Read clicks, impressions, CTR, average position, and indexing details from Google Search Console properties you choose to share.
- Run browser tasks on your website with Max, or generate sitemap and llms.txt drafts and check agent readiness.
For example, ask which pages lost Google clicks, choose a page to audit, and work through its first fix in the same conversation. Access to each step depends on your plan and the permissions you grant.
1. Sign in to Layzr
Open Connect your assistant and sign in. Use the account whose audits, websites, and subscription you want to access. You can start with Free.
If you want to use Search Console, enable your selected properties on that page before connecting the assistant. The Search Console steps below explain how.
2. Connect Codex
With Node.js and npm installed, copy this command into your terminal. It runs the official Codex CLI through npx, so a separate global codex command is not required.
npx -y @openai/codex mcp add layzr --url https://www.layzr.ai/api/mcp- Run the command. If the terminal prints an authorization link, open it in your browser.
- Sign in to Layzr, review the requested permissions, and select Allow connection.
- Return to your terminal. A successful connection shows Successfully logged in.
If adding the server does not start sign-in, run this command:
npx -y @openai/codex mcp login layzr- Codex installation optionsOfficial OpenAI instructions for installing and signing in to Codex.
- Codex MCP commandsOfficial reference for connecting and authenticating MCP servers.
3. Try your first request
Open a new Codex task and paste this prompt. Reading your account and saved reports does not consume audit credits.
Prompt
Use Layzr to show my subscription, remaining allowances, and saved audits. Don’t run an audit or any other usage-consuming tools.
Check that the returned plan matches your account. When you are ready to use an audit allowance, replace the example URL in this prompt with your website:
Prompt
Use Layzr to audit https://example.com exactly once. Explain the first actionable fix, then show my remaining audit credits and saved audits.
The audit returns a report you can also open in Layzr. Free accounts get the first actionable fix, one clarification, and one recheck. Ask for a recheck after applying the fix to your website.
An audit can take a few minutes. If your assistant times out, ask it to retrieve the original operation using its request ID before starting another audit.
Connect another assistant
Use an assistant that supports remote MCP servers over Streamable HTTP with OAuth sign-in. Its setup screen may call this a custom connector, integration, or MCP server. Add the URL below and follow its sign-in flow.
https://www.layzr.ai/api/mcpChoose OAuth authentication and approve the connection in Layzr. The server URL is enough to start discovery; you do not paste Google credentials or a Layzr password into your assistant. Client support and setup menus vary.
Your plan and allowances
The assistant uses the same subscription and allowances as the website. Running an audit in one place reduces the allowance in both. Upgrades and downgrades apply when the assistant next calls a tool.
| Allowance | Free · $0 | Pro · $9/month | Max · $29/month |
|---|---|---|---|
| Audits and follow-up answers | 1 lifetime audit, 1 clarification | 500 / month | 1500 / month |
| Website workspaces | 1 | 1 | 3 |
| Tracked pages per website | — | 1 | 10 |
| AI visibility providers | — | OpenAI | 8 providers |
| Saved prompts per page | — | 5 | 15 |
| Web-enabled prompt runs | — | 5 / week | 15 / week |
| Browser agent tasks | — | — | 25 / month |
| Search Console | — | Selected properties | Selected properties |
Prices are in USD. Free supports a general desktop audit and one recheck of the first applied fix. Pro and Max unlock the full audit report, additional audit types, and mobile audits. See pricing for the full plan details.
Share selected Search Console properties
Search Console access is included in Pro and Max. It needs both a Google connection and your permission to share selected properties with an assistant.
- Open Connect your assistant and choose Connect Google under Search Console access.
- Sign in to a Google account with access to your Search Console properties.
- Select the properties you want to share and choose Allow selected properties.
- Connect or reconnect your assistant and approve the Search Console permission. Newly added properties require a fresh assistant connection.
Prompt
Use Layzr to list my connected Search Console properties. For the property I choose, compare the last 28 days with the previous 28 days and show which pages lost the most clicks.
Google credentials stay with Layzr. Requested results are sent to your assistant, including search queries and page performance. Search Console reports Google search activity; measuring sales or signups requires a separate source of conversion data.
Control what your assistant can access
The consent screen separates reading account data, running tools, managing saved data, and reading selected Search Console properties. Select the permissions you want to grant. Running tools can use allowances; management tools can change saved prompts and monitoring settings.
To stop access, open Connect your assistant and choose Disconnect beside the assistant. Remove assistant access under Search Console to stop sharing Google data. Disconnecting stops future access; results already sent to an assistant follow that assistant’s data policies.
If something does not work
- Command not found: the setup command uses npx. If npx is missing, install Node.js and npm, or use the official Codex installation options above and run the command with codex instead of npx -y @openai/codex.
- Connected, but no tools appear: start a new task or refresh the assistant’s MCP connection. If the connection has expired, run the sign-in command again.
- The wrong plan appears: check the account signed in on Layzr’s Connect page. Disconnect and sign in with the intended account.
- Search Console is unavailable: check your plan, the selected properties, and the assistant’s Search Console permission. Reconnect after adding properties.
- An allowance is exhausted: ask for your current usage. Reading saved audits remains available without starting another audit.
FAQ
Do I need a separate Layzr MCP subscription?
No. MCP uses your existing Free, Pro, or Max plan. Allowances are shared between your assistant and the Layzr website.
Can I start without paying?
Yes. Free includes one general desktop audit, the first actionable fix, one clarification, and one recheck. You can also read your saved reports and account allowances.
Will Layzr automatically change my website?
Audit tools return findings and recommendations. Sitemap and llms.txt generators return drafts for you to publish. Browser agent tasks on Max can interact with a website, so specify the actions you want and review them before running a task.
Connect your assistant to Layzr
Sign in, check your plan, and choose what your assistant can access.
Open connection settings