OpenReview MCP Server
# OpenReview MCP Server
[](LICENSE)
[](https://www.python.org/downloads/)
An MCP server that connects Claude to [OpenReview](https://openreview.net) for conference reviewer and area chair workflows.
## Setup
1. Install dependencies:
```bash
cd openreview-mcp
uv sync
```
2. Create a `.env` file from the example:
```bash
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
```
## Claude Code Configuration
Add to `~/.claude/settings.json`:
```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
```bash
uv sync --all-extras
uv run pytest
```
See [CONTRIBUTING.md](CONTRIBUTING.md) for details.
## License
MIT — see [LICENSE](LICENSE) for details.
TDQS
Scored across 13 tools
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.
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.
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).
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.