Optiqra Mcp

io.github.armin5872Published by GitHub account armin5872v1.0.4Updated Oct 24, 2026

MCP server exposing OptiQra's website audit tools: SEO, GEO, AEO, and AI-generated fixes.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Local MCP server that exposes OptiQra's website audit API, letting an assistant crawl a URL for SEO/GEO/AEO issues and generate AI fixes and insights.

What you can do
Run a full SEO, GEO, AEO, performance, accessibility and security audit on a URL by crawling it and returning a report with issues and scores, plus AI-written fixes for individual issues and a site-wide AI strategy summary across a full report. Check that an AI provider, API key and model combination works before using the AI tools.
When to use it
Useful when you want an assistant to audit a website's search and AI-visibility readiness, explain the findings, and draft concrete fixes without leaving the chat. Also handy for validating an AI provider key before running the AI fix or insights tools.
Requirements
Runs locally over stdio, typically via npx or node. Node.js is needed. Optional environment variables: OPTIQRA_BASE_URL (defaults to the public demo instance), OPTIQRA_PROVIDER_API_KEY for the AI tools, and OPTIQRA_TIMEOUT_MS (default 120000). Network access to the OptiQra instance and the chosen AI provider is required.
Before you install
The AI tools need an AI-provider API key; setting OPTIQRA_PROVIDER_API_KEY in the client config is preferred over passing it through chat. The README states the key is forwarded to the provider and not stored, but it still leaves your machine. By default requests go to a public demo instance; point OPTIQRA_BASE_URL at your own deployment if audit data is sensitive. Full-site crawls can be slow.

Installation

In SourceWeft

  1. Open Optiqra Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

optiqra-mcp

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:

ToolOptiQra endpointWhat it does
optiqra_analyzePOST /api/analyzeCrawls a URL and runs the full SEO/GEO/AEO/perf/a11y/security audit
optiqra_ai_fixPOST /api/ai-fixGenerates an AI-written fix for one issue from a report
optiqra_ai_insightsPOST /api/ai-insightsGenerates a site-wide AI strategy summary across a full report
optiqra_ai_testPOST /api/ai-testVerifies 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.

Install

bash
npm install

(or, once published, npm install -g optiqra-mcp / run directly with npx optiqra-mcp)

Configuration (environment variables)

VariableRequiredPurpose
OPTIQRA_BASE_URLNoBase URL of the OptiQra instance to call. Defaults to https://optiqra.vercel.app.
OPTIQRA_PROVIDER_API_KEYNoA default AI-provider API key used by optiqra_ai_fix/optiqra_ai_insights/optiqra_ai_test if the model doesn't pass one. Recommended over letting the model handle the key in plaintext.
OPTIQRA_TIMEOUT_MSNoRequest timeout in ms. Defaults to 120000 (full-site crawls can be slow).

Run it standalone

bash
node src/index.js

It speaks MCP over stdio, so you won't see anything happen — it's waiting for an MCP client to connect.

Wire it into an MCP client

Claude Desktop / Claude Code

Add to your MCP config (claude_desktop_config.json, or via claude mcp add for Claude Code):

json
{  "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 configfile lives.
## Notes on the AI-key tools
`optiqra_ai_fix`, `optiqra_ai_insights`, and `optiqra_ai_test` all need aprovider API key, exactly like pasting one into OptiQra's own UI — OptiQra'sserver forwards it straight to the provider (OpenAI, Anthropic, Google, Groq,OpenRouter, Mistral, DeepSeek, or xAI) and never stores it. This server doesthe 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 throughchat.

Source: README.md at commit d053955

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts