io.github.armin5872/optiqra-mcp

Registre officiel Marketing et ventes

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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package optiqra-mcp
Claude Code
claude mcp add optiqra-mcp -e 'OPTIQRA_BASE_URL=<OPTIQRA_BASE_URL>' -e 'OPTIQRA_PROVIDER_API_KEY=<your optiqra_provider_api_key>' -e 'OPTIQRA_TIMEOUT_MS=<OPTIQRA_TIMEOUT_MS>' -- npx -y optiqra-mcp@1.0.4
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "optiqra-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "optiqra-mcp@1.0.4"
            ],
            "env": {
                "OPTIQRA_BASE_URL": "<OPTIQRA_BASE_URL>",
                "OPTIQRA_PROVIDER_API_KEY": "<your optiqra_provider_api_key>",
                "OPTIQRA_TIMEOUT_MS": "<OPTIQRA_TIMEOUT_MS>"
            }
        }
    }
}

Variables d'environnement

  • OPTIQRA_BASE_URL Base URL of the OptiQra instance to call. Defaults to https://optiqra.vercel.app.
  • OPTIQRA_PROVIDER_API_KEY secret Default AI-provider API key used by the ai-fix/ai-insights/ai-test tools if the caller doesn't pass one.
  • OPTIQRA_TIMEOUT_MS Request timeout in milliseconds. Defaults to 120000.

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. optiqra-mcp
  2. Install
  3. Configuration (environment variables)
  4. Run it standalone
  5. Wire it into an MCP client

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

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

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):

{
  "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.

Questions fréquentes

Qu'est-ce que io.github.armin5872/optiqra-mcp ?

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

Comment installer io.github.armin5872/optiqra-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add optiqra-mcp -e 'OPTIQRA_BASE_URL=<OPTIQRA_BASE_URL>' -e 'OPTIQRA_PROVIDER_API_KEY=<your optiqra_provider_api_key>' -e 'OPTIQRA_TIMEOUT_MS=<OPTIQRA_TIMEOUT_MS>' -- npx -y optiqra-mcp@1.0.4. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.armin5872/optiqra-mcp ?

Oui. Il attend OPTIQRA_PROVIDER_API_KEY, à renseigner dans sa configuration.

io.github.armin5872/optiqra-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.armin5872/optiqra-mcp ?

Il est publié par armin5872. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.