Codex plugin catalog MCP

Connect

Configured Streamable HTTP endpoint: https://appcorpus.com/mcp/codex. Public reads need no installer or credentials unless the host operator has separately configured transport authentication.

For ChatGPT, add a remote MCP connector using the endpoint above and choose no authentication when that option is available. In Codex, Claude Code, Cursor, or another standard Streamable HTTP client, use the matching configuration form below. Host interfaces may differ.

Codex CLI / IDE

[mcp_servers.codex_apps]
url = "https://appcorpus.com/mcp/codex"

Claude Code

{
  "mcpServers": {
    "codex-apps": {
      "type": "http",
      "url": "https://appcorpus.com/mcp/codex"
    }
  }
}

Cursor

{
  "mcpServers": {
    "codex-apps": {
      "url": "https://appcorpus.com/mcp/codex"
    }
  }
}

Both JSON examples use the standard remote HTTP server URL shape. Generic clients can use the same endpoint as a Streamable HTTP server.

Protocol checks with curl

Initialize the protocol, then list the available tools. The server uses stateless HTTP and does not require a session ID:

curl -i https://appcorpus.com/mcp/codex -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"codex-mcp-client","version":"1.0.0"}}}'

curl -i https://appcorpus.com/mcp/codex -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

The endpoint uses stateless JSON-RPC over Streamable HTTP. The examples show the request bodies for protocol initialization, tool listing, and tool calls.

Contract and metadata

Codex module and contract version: 1.0.0.

• Server card
• Module manifest
• Tool schemas
• Contract version 1.0.0 is included with the tool input and output schemas.

Read-only tools

Search takes a required query (1–2000 characters), with optional category, sort, limit (1–10, default 5), and offset (0–1000). Detail takes a required app reference. Category listing takes no arguments. Comparison takes two to five app references and compares distinct resolved products. The examples use the current public slugs Qodo and Linear.

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "search_codex_apps",
    "arguments": {
      "query": "calendar",
      "limit": 5,
      "sort": "relevance"
    }
  }
}

curl -i https://appcorpus.com/mcp/codex -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"search_codex_apps","arguments":{"query":"calendar","limit":5,"sort":"relevance"}}}'

{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "get_codex_app",
    "arguments": {
      "app": "qodo"
    }
  }
}

curl -i https://appcorpus.com/mcp/codex -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"get_codex_app","arguments":{"app":"qodo"}}}'

{
  "jsonrpc": "2.0",
  "id": 5,
  "method": "tools/call",
  "params": {
    "name": "list_codex_categories",
    "arguments": {}
  }
}

curl -i https://appcorpus.com/mcp/codex -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":5,"method":"tools/call","params":{"name":"list_codex_categories","arguments":{}}}'

{
  "jsonrpc": "2.0",
  "id": 6,
  "method": "tools/call",
  "params": {
    "name": "compare_codex_apps",
    "arguments": {
      "apps": [
        "qodo",
        "linear"
      ]
    }
  }
}

curl -i https://appcorpus.com/mcp/codex -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":6,"method":"tools/call","params":{"name":"compare_codex_apps","arguments":{"apps":["qodo","linear"]}}}'

Source and limits

• All four tools are public reads: search, app detail, category listing, and comparison. They do not install or execute plugins.
• The service reports registry/source metadata and declared authentication or installation policies. These policies describe the plugin; they are not connection methods provided by this MCP.
• Capabilities and descriptions are source metadata. Missing values remain unknown; do not infer price, popularity, installs, compatibility, or security from absence or from a listing.
• Codex data is sourced from two official registries. The page and result records expose source/registry commit dates and checked timestamps separately; a snapshot date is not a per-record observation date.
• External review metadata is limited to the packages explicitly linked in source records. It does not imply all listed packages were independently reviewed.

Search, detail, category listing, and comparison are public reads. They do not install, execute, configure, or authorize a plugin. The authentication and installation fields describe registry policy only. Price and popularity are unsupported unless a future contract provides explicit sourced fields; they are not inferred from registry ordering.

For the separate AppAthlas mobile-app discovery MCP, see AppAthlas agents. Browse Codex registry listings at Codex plugins.