Skip to main content
Glama
OpenReview MCP Server
by qizhex

OpenReview MCP Server

License: MIT Python 3.10+

An MCP server that connects Claude to OpenReview for conference reviewer and area chair workflows.

Setup

  1. Install dependencies:

    cd openreview-mcp
    uv sync
  2. Create a .env file from the example:

    cp .env.example .env
  3. Edit .env with your OpenReview credentials:

    OPENREVIEW_USERNAME=your_email@example.com
    OPENREVIEW_PASSWORD=your_password
    OPENREVIEW_BASEURL=https://api2.openreview.net

Related MCP server: GitHub MCP Server

Claude Code Configuration

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "openreview": {
      "command": "uv",
      "args": ["run", "--directory", "/path/to/openreview-mcp", "python", "-m", "openreview_mcp"]
    }
  }
}

Available Tools

Read Tools

  • list_venues — List venues where you have active roles

  • list_assignments — List papers assigned to you

  • get_submission — Get full submission details

  • get_pdf — Download a paper's PDF for analysis

  • get_reviews — Get all reviews for a paper

  • get_review_status — Check review completion across your assigned papers

  • get_discussion — Get discussion threads on a paper

Write Tools (preview + confirm)

  • submit_review — Prepare and submit a review

  • edit_review — Edit your existing review

  • submit_meta_review — Prepare and submit a meta-review

  • post_comment — Post a comment on a submission

  • message_reviewer — Send a private message to a reviewer (visible to ACs, SACs, PCs)

  • confirm_submission — Confirm and post a pending write action

Write tools return a preview first. You must call confirm_submission with the confirmation ID to actually post to OpenReview.

Development

uv sync --all-extras
uv run pytest

See CONTRIBUTING.md for details.

License

MIT — see LICENSE for details.

Available Tools

13 tools
confirm_submissionA

Confirm and submit a pending review, meta-review, or comment to OpenReview.

Args: confirmation_id: The confirmation ID returned by submit_review, submit_meta_review, post_comment, or message_reviewer.

Inputs: confirmation_id (required). Returns: result

edit_reviewA

Edit your existing review. Returns a preview — call confirm_submission to actually post the edit.

Args: venue_id: The venue identifier. submission_number: The paper number. review_text: Updated review text. rating: Updated rating. confidence: Updated confidence. title: Updated title. strengths: Updated strengths. weaknesses: Updated weaknesses. questions: Updated questions.

Inputs: venue_id (required), submission_number (required), review_text, rating, +5 more. Returns: result

get_discussionA

Get all discussion comments on a submission (rebuttals, reviewer responses, AC comments).

Args: venue_id: The venue identifier. submission_id: The submission's note ID. Provide this OR submission_number. submission_number: The paper number. Provide this OR submission_id.

Inputs: venue_id (required), submission_id, submission_number. Returns: result

get_pdfA

Download a submission's PDF and return the file path so you can read it.

Args: venue_id: The venue identifier (e.g., 'ICLR.cc/2025/Conference'). submission_id: The submission's note ID. Provide this OR submission_number. submission_number: The submission's paper number. Provide this OR submission_id.

Inputs: venue_id (required), submission_id, submission_number. Returns: result

get_reviewsA

Get all official reviews for a submission.

Args: venue_id: The venue identifier (e.g., 'ICLR.cc/2025/Conference'). submission_id: The submission's note ID. Provide this OR submission_number. submission_number: The paper number. Provide this OR submission_id.

Inputs: venue_id (required), submission_id, submission_number. Returns: result

get_review_statusB

Check review completion status for all your assigned papers.

Args: venue_id: The venue identifier. role: Your role — 'reviewer', 'area_chair', or 'senior_area_chair'. Default: 'area_chair'.

Inputs: venue_id (required), role. Returns: result

get_submissionA

Get full details of a submission (title, abstract, authors, keywords, etc.).

Args: venue_id: The venue identifier (e.g., 'ICLR.cc/2025/Conference'). submission_id: The submission's note ID. Provide this OR submission_number. submission_number: The submission's paper number. Provide this OR submission_id.

Inputs: venue_id (required), submission_id, submission_number. Returns: result

list_assignmentsA

List papers assigned to you for a given venue.

Args: venue_id: The venue identifier (e.g., 'ICLR.cc/2025/Conference'). Use list_venues to find this. role: Your role — 'reviewer', 'area_chair', or 'senior_area_chair'. Default: 'reviewer'.

Inputs: venue_id (required), role. Returns: result

list_venuesA

List all OpenReview venues where you have an active role (Reviewer, Area Chair, or Senior Area Chair).

Inputs: no named parameters. Returns: result

message_reviewerA

Send a private message to a specific reviewer. Visible to the reviewer, ACs, SACs, and PCs.

Returns a preview — call confirm_submission to actually send it.

Args: venue_id: The venue identifier. submission_number: The paper number. reviewer_id: The reviewer's anonymous ID (e.g., 'Reviewer_ABCD'). subject: Message subject line. message_text: Message body.

Inputs: venue_id (required), submission_number (required), reviewer_id (required), subject (required), +1 more. Returns: result

post_commentA

Post a comment on a submission. Returns a preview — call confirm_submission to post it.

Default readers include ACs, SACs, and PCs. Override with the readers parameter.

Args: venue_id: The venue identifier. submission_number: The paper number. comment_text: The comment text. readers: Who can see this comment. Defaults to ACs + SACs + PCs + Reviewers for the paper.

Inputs: venue_id (required), submission_number (required), comment_text (required), readers. Returns: result

submit_meta_reviewA

Prepare a meta-review for submission. Returns a preview — call confirm_submission to post it.

Args: venue_id: The venue identifier. submission_number: The paper number. recommendation: Your recommendation (e.g., 'Accept', 'Reject', 'Accept (Poster)', etc.). metareview_text: The meta-review text summarizing reviews and your assessment. confidence: Your confidence level (scale depends on venue).

Inputs: venue_id (required), submission_number (required), recommendation (required), metareview_text (required), +1 more. Returns: result

submit_reviewA

Prepare a review for submission. Returns a preview — call confirm_submission to actually post it.

Args: venue_id: The venue identifier. submission_number: The paper number. rating: Numerical rating (scale depends on venue). confidence: Your confidence level (scale depends on venue). review_text: The main review text. title: Review title. Default: 'Official Review'. strengths: Paper strengths (if venue uses separate fields). weaknesses: Paper weaknesses (if venue uses separate fields). questions: Questions for the authors. limitations: Limitations discussion. ethics_flag: Whether to flag ethics concerns.

Inputs: venue_id (required), submission_number (required), rating (required), confidence (required), +7 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a distinct purpose with clear boundaries: list_venues, list_assignments, get_submission, get_pdf, get_reviews, get_discussion, get_review_status, submit_review, submit_meta_review, edit_review, post_comment, message_reviewer, and confirm_submission. There is no overlap or ambiguity between tools; for example, get_reviews retrieves existing reviews while submit_review creates new ones, and confirm_submission is uniquely for finalizing pending actions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., list_venues, get_submission, submit_review, post_comment). The verbs are descriptive and appropriate for their actions (list, get, submit, post, edit, message, confirm), and there are no deviations in style or convention across the 13 tools.

    Tool Count5/5

    With 13 tools, this server is well-scoped for the OpenReview domain, covering key workflows like venue listing, assignment management, submission retrieval, review/meta-review creation and editing, commenting, messaging, and confirmation. Each tool serves a specific, necessary function without bloat, and the count aligns with typical MCP servers (3-15 tools).

    Completeness5/5

    The tool set provides comprehensive coverage for the OpenReview peer-review domain, including CRUD-like operations: listing venues and assignments, retrieving submissions and related data (PDFs, reviews, discussions), creating and editing reviews/meta-reviews/comments/messages, and confirming submissions. There are no obvious gaps; agents can perform full review workflows from start to finish without dead ends.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects your Zotero research library with Claude and other AI assistants via the Model Context Protocol, allowing you to search your library, access content, discuss papers, get summaries, and analyze citations.
      35
      11,253 PyPI
      5,941
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude to GitHub repositories for querying repos, reviewing PRs, managing issues, searching code, and automating workflows.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Connects Claude to Apple's App Store Connect API, letting you manage apps, builds, TestFlight beta groups and testers, customer reviews and replies, sales and finance reports, and team users through natural language. Write actions such as invites, beta review submissions, and review responses require confirmation before anything is sent.
      22
      447 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables pre-submission review of ML papers inside Claude Code or Claude Desktop by checking format and anonymization risks, resolving every reference, finding prior work for each claim, verifying quotes against the PDF, and running methodology and writing checks. It reports findings only, never scores, ratings, or accept/reject verdicts, and never rewrites the author's text.
      7
      MIT