AOPX

Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Selects between supported SEARCH providers for ECONOMY or CRITICAL mode.

    How to connect

    How to connect AOPX to Claude

    The server address to paste into Claude settings:

    https://api.aopx.fr/mcp/

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect AOPX to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.aopx.fr/mcp/

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect AOPX to Cursor

    The server address to paste into Cursor settings:

    https://api.aopx.fr/mcp/

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (4)

    Raw names from tools/list. Only developers need these.

    recommend_providerUse when a software agent needs an AOPX recommendation for the SEARCH category instead of hard-coding a single supported provider. Supported modes are ECONOMY and CRITICAL. Returns a primary provider and, when applicable, a fallback provider plus a recommendation_id. AOPX does not execute the search and does not handle payment; the caller executes the provider path externally. After a real execution, call report_outcome with the same recommendation_id. max_cost_eur and max_latency_ms are accepted and recorded by the current v0 interface but are not enforced as hard routing constraints.
    report_outcomeUse only after a real external execution of a provider path returned by recommend_provider. Records the caller-reported production outcome for that recommendation_id. The recommendation must exist, only one outcome is accepted per recommendation, and provider attempts must match the recommended primary/fallback path. Reported outcomes are production evidence supplied by the caller; they are not described as independently verified outcomes.
    public_statsRead aggregate public statistics from the AOPX production pilot, including consultation and reported-outcome activity. Use this for public telemetry, not for provider recommendation. LAB benchmarks, tests, shadow runs and replay events are excluded from these production statistics.
    public_outcomesRead recent caller-reported production outcomes from the AOPX public evidence surface. Use this to inspect what was reported after real recommendations were executed, not to request a new recommendation. Provider identities are exposed only through public aliases. LAB benchmarks, tests, shadow runs and replays are not returned here, and reported outcomes are not described as independently verified.