Log inSubmit server
Openreview logo

Openreview

Searches OpenReview venues, submissions, papers, reviews, comments, and decisions through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Openreview

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "openreview": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openreview"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 6 tools correctly (6d ago).

Overview

Openreview MCP server connects AI agents to OpenReview's API v2 for machine-learning conference venues, submissions, and peer-review data. It provides tools for finding venues, searching topic-matched submissions and notes, and retrieving venue metadata. Public reads work without credentials, while restricted data can use an optional token. Reach for it when an agent needs structured research across venues such as ICLR, NeurIPS, ICML, COLM, or EMNLP.

Use cases

  • Find papers matching a research topic at a specific ML venue
  • Compare reviews, rebuttals, and decisions for a paper
  • Search OpenReview notes across selected conferences
  • Inspect venue metadata and publication history

Key features

  • Venue discovery and metadata lookup
  • Topic-based submission search
  • Full-text note search
  • Paper thread retrieval
  • Optional OpenReview token support
  • Hosted or standalone MCP operation

Tools6

What Openreview lets your agent do. Expand a tool for its parameters.

Verified live~695 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

What it can do

From the 6 tools this server returned when we ran it.

Read-only tools · 6
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age157 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-openreview (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads463Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed6Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Openreview works

What the Openreview MCP server does

The Openreview MCP server exposes selected OpenReview data through the Model Context Protocol. It is intended for research workflows involving machine-learning conference venues and their associated submissions, reviews, rebuttals, comments, and decisions. The upstream source is OpenReview's API v2, with the v1 host available for legacy venues.

The server can identify active or historical venues, return metadata for a specific venue group, search submissions by topic, perform full-text searches over notes, and retrieve individual records when the upstream read path permits it. A paper-level lookup is designed to return the paper together with its discussion threads.

How it works

The packaged tools call OpenReview endpoints beneath api2.openreview.net. Venue operations use the groups API. Note searches use /notes/search, while individual note and paper retrieval use the /notes path. Searches can be limited by venue, content field, signature, result count, and offset, depending on the tool.

The project can be used in two ways. A hosted MCP endpoint is available through the Pipeworx gateway, where the connection also exposes shared gateway meta-tools. A local package can instead run over standard input and output using npx; that mode exposes only the OpenReview-specific tools. The gateway also offers HTTP calls for invoking tools without an MCP client.

Setup and configuration

For a hosted connection, add the Pipeworx MCP URL to a compatible client. The standalone configuration runs @pipeworx/mcp-openreview with npx -y, requiring no Pipeworx account or gateway round trip. The local process communicates over stdin and stdout.

Public reads are keyless. Restricted venues or private invitations may require an OpenReview token. A gateway deployment can receive the optional PLATFORM_OPENREVIEW_TOKEN setting. Alternatively, a caller can provide a token through the _apiKey query parameter after obtaining it from OpenReview. Authentication is not a workaround for the upstream challenge affecting individual note reads.

Tools and capabilities

Available OpenReview MCP server tools include:

  • list_venues: find active and historical venues with optional query, limit, and offset values.
  • get_venue: retrieve metadata for a venue or group ID.
  • list_submissions: search submissions within a venue by topic, with pagination.
  • get_note: request one paper, review, comment, or decision by note ID, with optional details.
  • get_paper: request a paper and its related review, rebuttal, and decision threads by forum ID.
  • search_notes: run full-text searches and optionally constrain them by content field, signature, venue, limit, or offset.

The hosted gateway additionally lists shared tools such as ask_pipeworx, discover_tools, search_within, and memory operations. Those shared tools are gateway features, not part of the standalone package.

Limitations and notes

As of the README's September 1, 2026 verification, automated GET /notes requests receive a 403 ChallengeRequiredError from both the v2 and legacy hosts. This occurs with or without a token and across different clients. Consequently, get_note and get_paper report an upstream failure rather than a credential error.

Venue listing and metadata remain available, and note search continues to work. list_submissions now relies on topic-based note search, so a topic-less request for every submission in a venue is not available to automated clients. When a paper read is blocked, use search_notes to locate it or open https://openreview.net/forum?id=<forum_id> directly.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openreview

Openreview is an MCP server that connects AI agents to OpenReview's v2 API for machine-learning conference venues, submissions, papers, reviews, comments, and decisions. Its main tools list venues, retrieve venue metadata, search submissions and notes, fetch individual notes, and assemble a paper's discussion threads.

Run `npx -y @pipeworx/mcp-openreview` as a local stdio server, or configure an MCP client with the hosted URL `https://gateway.pipeworx.io/openreview/mcp`. The local option does not require a Pipeworx account.

Yes, Openreview works with Cursor through the hosted MCP endpoint. Add `https://gateway.pipeworx.io/openreview/mcp` to Cursor's MCP configuration, or configure the local `npx` stdio command.

OpenReview's `/notes` read endpoint currently returns `403 ChallengeRequiredError` to automated clients, while `/notes/search` remains available. Use `search_notes` to locate records or open the paper's OpenReview forum URL directly.

No, public reads are keyless. Restricted venues and private invitations may need an optional OpenReview token, supplied through `PLATFORM_OPENREVIEW_TOKEN` on the gateway or `_apiKey` for a request.

Related MCP servers

All in Research All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenreview AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/openreview?style=directory)](https://allmcps.com/mcp/openreview)
HTML Embed
<a href="https://allmcps.com/mcp/openreview"><img src="https://allmcps.com/api/badge/openreview?style=directory" alt="Openreview on AllMCPs" /></a>