Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@optiqra-mcp Run a full SEO audit on https://mystore.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP (Model Context Protocol) server that exposes every tool in OptiQra's API to MCP-compatible AI clients (Claude Desktop, Claude Code, Cursor, etc.).
OptiQra has four HTTP endpoints. This server wraps all four as MCP tools:
Tool | OptiQra endpoint | What it does |
|
| Crawls a URL and runs the full SEO/GEO/AEO/perf/a11y/security audit |
|
| Generates an AI-written fix for one issue from a report |
|
| Generates a site-wide AI strategy summary across a full report |
|
| Verifies a provider/API key/model combo works before using the two above |
By default it talks to the public demo, https://optiqra.vercel.app. Point
it at your own deployment (see OptiQra's own DEPLOYMENT.md/Docker setup)
with an env var — see below.
npm install(or, once published, npm install -g optiqra-mcp / run directly with npx optiqra-mcp)
Related MCP server: mcp-seo
Variable | Required | Purpose |
| No | Base URL of the OptiQra instance to call. Defaults to |
| No | A default AI-provider API key used by |
| No | Request timeout in ms. Defaults to |
node src/index.jsIt speaks MCP over stdio, so you won't see anything happen — it's waiting for an MCP client to connect.
Add to your MCP config (claude_desktop_config.json, or via claude mcp add
for Claude Code):
{
"mcpServers": {
"optiqra": {
"command": "node",
"args": ["/absolute/path/to/optiqra-mcp/src/index.js"],
"env": {
"OPTIQRA_BASE_URL": "https://optiqra.vercel.app",
"OPTIQRA_PROVIDER_API_KEY": "sk-..."
}
}
}
}
Any other MCP-compatible client (Cursor, Windsurf, etc.) uses the same
`command`/`args`/`env` shape — check that client's docs for where the config
file lives.
## Notes on the AI-key tools
`optiqra_ai_fix`, `optiqra_ai_insights`, and `optiqra_ai_test` all need a
provider API key, exactly like pasting one into OptiQra's own UI — OptiQra's
server forwards it straight to the provider (OpenAI, Anthropic, Google, Groq,
OpenRouter, Mistral, DeepSeek, or xAI) and never stores it. This server does
the same: it never persists keys. Prefer setting `OPTIQRA_PROVIDER_API_KEY`
in your MCP client's env config over having the model pass a key through
chat.Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
SEO research, audits, backlinks, GSC, and content workflow tools for AI agents.
SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.
Live SEO workflow tools for Claude Code, Codex, and AI agents.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/armin5872/optiqra-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server